Triple
T28369048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles III of Ireland |
E718572
|
entity |
| Predicate | titleHolderAlternativeName |
P58984
|
FINISHED |
| Object | the Young Pretender |
—
|
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: the Young Pretender | Statement: [Charles III of Ireland, titleHolderAlternativeName, the Young Pretender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderAlternativeName Context triple: [Charles III of Ireland, titleHolderAlternativeName, the Young Pretender]
-
A.
hasTitleHolderAlternativeName
chosen
Indicates that an entity serving as a title holder is known by an alternative or additional name.
-
B.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
C.
titleHolderKnownAs
Indicates that the person holding a particular title is commonly referred to or known by a specified name or alias.
-
D.
titleHolderFullName
Indicates the full personal name of the entity that holds a particular title or position.
-
E.
titleHolderGivenName
Indicates that the predicate specifies the given (first) name of the person who holds a particular title.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 12:58 a.m.