Triple
T20244352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry II of Jerusalem |
E498382
|
entity |
| Predicate | reignAsTitularKingOfJerusalemTo |
P36568
|
FINISHED |
| Object | 1324 |
—
|
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: 1324 | Statement: [Henry II of Jerusalem, reignAsTitularKingOfJerusalemTo, 1324]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsTitularKingOfJerusalemTo Context triple: [Henry II of Jerusalem, reignAsTitularKingOfJerusalemTo, 1324]
-
A.
reignAsKingOfJerusalemEnd
chosen
Indicates the point in time or event at which an individual’s reign as king of Jerusalem comes to an end.
-
B.
reignAsKingOfJerusalemStart
Indicates the time at which an individual begins their reign as king of Jerusalem.
-
C.
ruledInExileAsPrinceOfAntioch
Indicates that a person continued to exercise princely authority over Antioch while living outside the territory, governing it in exile rather than from within the principality.
-
D.
successorAsTitularKing
Indicates that one entity becomes the next holder of a ceremonial or nominal kingship position previously held by another entity.
-
E.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a10ab48190a408a5d2c2b0808b |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.