Triple
T37559584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormond, Ireland |
E933779
|
entity |
| Predicate | linkedToTitleInPeerage |
P64418
|
FINISHED |
| Object | Peerage of Ireland |
—
|
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: Peerage of Ireland | Statement: [Ormond, Ireland, linkedToTitleInPeerage, Peerage of Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToTitleInPeerage Context triple: [Ormond, Ireland, linkedToTitleInPeerage, Peerage of Ireland]
-
A.
linkedToPeerage
chosen
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
B.
linkedNobleTitleSpelling
Indicates that two noble titles are associated with each other as alternative or related spellings of the same title.
-
C.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
D.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
E.
titleHolderOfficeBeforePeerage
Indicates that the person holding a title previously held a specific office before being elevated to the peerage.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:17 p.m.