Triple
T35376858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O’Connell Tower |
E1022536
|
entity |
| Predicate | notableBurialAssociated |
P3803
|
FINISHED |
| Object | Daniel O’Connell |
E406964
|
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: Daniel O’Connell | Statement: [O’Connell Tower, notableBurialAssociated, Daniel O’Connell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBurialAssociated Context triple: [O’Connell Tower, notableBurialAssociated, Daniel O’Connell]
-
A.
alsoBurials
Indicates that the subject location or record includes additional burial sites or burial events beyond the primary one referenced.
-
B.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
C.
hasNotableBurials
chosen
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
D.
cemeteryKnownFor
Indicates that a cemetery is notable or recognized for a particular person, event, feature, or characteristic.
-
E.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3840213f848190bb5134769199be7c |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.