Triple
T34225071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishamble Street |
E878021
|
entity |
| Predicate | hasCommemorativePlaqueFor |
P57238
|
FINISHED |
| Object | Handel’s Messiah |
E138183
|
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: Handel’s Messiah | Statement: [Fishamble Street, hasCommemorativePlaqueFor, Handel’s Messiah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorativePlaqueFor Context triple: [Fishamble Street, hasCommemorativePlaqueFor, Handel’s Messiah]
-
A.
hasCommemorativePlaques
chosen
Indicates that one entity possesses or displays commemorative plaques associated with it.
-
B.
commemoratedPerson
Indicates that the subject serves as a memorial or tribute to the referenced person.
-
C.
hasCommemorativeStructure
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
-
D.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
E.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36cc9a816081909e0a69426f97a96f |
completed | June 20, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.