Triple
T30529168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis II de Bourbon |
E776944
|
entity |
| Predicate | regentDuringEarlyCareer |
P71201
|
FINISHED |
| Object | Anne of Austria |
E1239028
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Anne of Austria | Statement: [Louis II de Bourbon, regentDuringEarlyCareer, Anne of Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regentDuringEarlyCareer Context triple: [Louis II de Bourbon, regentDuringEarlyCareer, Anne of Austria]
-
A.
reignAsRegentStart
Indicates the point in time when an individual begins exercising ruling authority as a regent on behalf of another.
-
B.
regentDuringEvent
chosen
Indicates that an individual served as regent (exercising ruling authority on behalf of another) during the time span of a specified event.
-
C.
regentFor
Indicates that one entity serves as the ruling authority on behalf of another, typically during the latter’s minority, absence, or incapacity.
-
D.
recognizedAsRegent
Indicates that an entity is formally acknowledged or designated as serving in the role of regent for another.
-
E.
regentPreviouslyHeldOffice
Indicates that the regent held a particular office or position before assuming their regency.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2856c775e48190aee2aef9a9afdb6d |
completed | June 9, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:18 p.m.