Triple
T5583333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adeliza of Louvain |
E146691
|
entity |
| Predicate | endTime (as Queen consort of England) |
P19030
|
FINISHED |
| Object | 1135 |
—
|
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: 1135 | Statement: [Adeliza of Louvain, endTime (as Queen consort of England), 1135]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTime (as Queen consort of England) Context triple: [Adeliza of Louvain, endTime (as Queen consort of England), 1135]
-
A.
endTimeAsQueenConsort
Indicates the date and time at which an individual’s tenure as queen consort comes to an end.
-
B.
reignAsQueenConsortOfEnglandEnd
chosen
Indicates the time or event at which an individual’s tenure as Queen Consort of England comes to an end.
-
C.
endTime (spouse Edward VIII)
Indicates the time at which the marital relationship with Edward VIII concluded.
-
D.
reignAsCountessConsortEnd
Indicates the date or point in time when an individual’s tenure as countess consort comes to an end.
-
E.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
- F. None of above.
Provenance (3 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02084b5f0819089b62283c57704ec |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.