Triple
T32127141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabella II of Jerusalem |
E820530
|
entity |
| Predicate | coronationAsQueenOfJerusalem |
P28655
|
FINISHED |
| Object | 1212 |
—
|
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: 1212 | Statement: [Isabella II of Jerusalem, coronationAsQueenOfJerusalem, 1212]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationAsQueenOfJerusalem Context triple: [Isabella II of Jerusalem, coronationAsQueenOfJerusalem, 1212]
-
A.
startTimeAsQueenConsortOfJerusalem
Indicates the date and time at which an individual began their tenure as Queen Consort of Jerusalem.
-
B.
coronationRight
Indicates the recognized right or entitlement of an entity to be crowned or to perform/receive a coronation.
-
C.
reignAsKingOfJerusalemEnd
Indicates the point in time or event at which an individual’s reign as king of Jerusalem comes to an end.
-
D.
coCoronationWith
Indicates that two or more individuals were crowned or formally installed into their positions in the same coronation ceremony.
-
E.
coronationEvent
chosen
Indicates the event in which a person is formally invested with royal authority and crowned as a monarch.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b96c2f0881908d14683ecfe1af4b |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.