Triple
T32127183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad II of Jerusalem |
E820531
|
entity |
| Predicate | successorAsKingOfJerusalem |
P66801
|
FINISHED |
| Object | Conradin |
—
|
NE NERFINISHED |
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: Conradin | Statement: [Conrad II of Jerusalem, successorAsKingOfJerusalem, Conradin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKingOfJerusalem Context triple: [Conrad II of Jerusalem, successorAsKingOfJerusalem, Conradin]
-
A.
successorAsKingOfKings
Indicates that one entity directly follows another in holding the title or role of King of Kings.
-
B.
successorAsTitularKing
chosen
Indicates that one entity becomes the next holder of a ceremonial or nominal kingship position previously held by another entity.
-
C.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
D.
reignAsKingOfJerusalemEnd
Indicates the point in time or event at which an individual’s reign as king of Jerusalem comes to an end.
-
E.
successorAsHighKing
Indicates that one entity becomes the next holder of the title or role of High King after another entity.
- 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_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 12:29 a.m.