Triple
T30077652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | le Poer |
E764364
|
entity |
| Predicate | notableTitleHeldByBearers |
P18924
|
FINISHED |
| Object | Earl of Tyrone |
E941899
|
NE 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: Earl of Tyrone | Statement: [le Poer, notableTitleHeldByBearers, Earl of Tyrone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTitleHeldByBearers Context triple: [le Poer, notableTitleHeldByBearers, Earl of Tyrone]
-
A.
notableTitleHeld
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
B.
notableBearerOfRole
Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
-
C.
notableOfficerTitle
chosen
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
D.
fieldOfNotableBearer
Indicates the professional or activity domain in which a notable bearer of a name, title, or identifier is recognized.
-
E.
hasNotableTitleHolderWhoBecame
Indicates that an entity has a notable title holder who later attained or transitioned into another specified role, status, or position.
- F. None of above.
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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27431e944481909f025d4e2f95f896 |
completed | June 8, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:02 p.m.