Triple
T1074306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor of Aquitaine |
E23800
|
entity |
| Predicate | marriageToHenryIIDate |
P23982
|
FINISHED |
| Object | 1152 |
—
|
LITERAL 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: 1152 | Statement: [Eleanor of Aquitaine, marriageToHenryIIDate, 1152]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToHenryIIDate Context triple: [Eleanor of Aquitaine, marriageToHenryIIDate, 1152]
-
A.
reignAsQueenConsortOfEnglandStart
Indicates the time at which an individual began serving as queen consort of England to a reigning English monarch.
-
B.
reignAsQueenConsortOfScotlandStart
Indicates the time at which a person began their tenure serving as queen consort of Scotland.
-
C.
reignAsQueenConsortOfEnglandEnd
Indicates the time or event at which an individual’s tenure as Queen Consort of England comes to an end.
-
D.
marriageThroughWhichTitleHeld
Indicates that a noble or formal title is held by a person specifically by virtue of (i.e., as a result of) a particular marriage.
-
E.
reignAsQueenConsortOfScotlandEnd
Indicates the time or event marking when an individual’s tenure as queen consort of Scotland comes to an end.
- F. None of above. chosen
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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92cbfd481909e2f928c1d06ebaa |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8d5076481908640a0d873efdf14 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.