Triple
T20244330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh I of Cyprus |
E498381
|
entity |
| Predicate | successorStatusAtAccession |
P139376
|
FINISHED |
| Object | infant son |
—
|
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: infant son | Statement: [Hugh I of Cyprus, successorStatusAtAccession, infant son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorStatusAtAccession Context triple: [Hugh I of Cyprus, successorStatusAtAccession, infant son]
-
A.
successorDesignationFor
Indicates the designation or identification of an entity that is intended to succeed or replace another entity in a given role, position, or function.
-
B.
successorFoundedBy
Indicates that an entity was founded by the successor of another specified entity.
-
C.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
-
D.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
E.
heldBySuccessorOf
Indicates that something is possessed, controlled, or occupied by an entity that is the successor of another specified entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.