Triple
T28351319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Rawdon |
E718105
|
entity |
| Predicate | notableBearerEthnicity |
P202902
|
FINISHED |
| Object | Anglo-Irish |
—
|
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: Anglo-Irish | Statement: [Baron Rawdon, notableBearerEthnicity, Anglo-Irish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerEthnicity Context triple: [Baron Rawdon, notableBearerEthnicity, Anglo-Irish]
-
A.
notableBearerNationality
Indicates that the subject has a notable bearer whose nationality is the specified object.
-
B.
associatedWithNotableBearerNationality
Indicates that an entity is connected to the nationality of a notable bearer of a related name or title.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
notableNationality
Indicates that an entity is notably associated with a particular nationality, often by origin, citizenship, or cultural identity.
-
E.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
| PDg | Predicate description generation | batch_6a00cda8ed348190950ee34bb24ae65b |
completed | May 10, 2026, 6:25 p.m. |
Created at: April 28, 2026, 12:46 a.m.