Triple
T10510650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Glade |
E247901
|
entity |
| Predicate | hasCommemorativeFocus |
P44944
|
FINISHED |
| Object | first responders |
—
|
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: first responders | Statement: [Memorial Glade, hasCommemorativeFocus, first responders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorativeFocus Context triple: [Memorial Glade, hasCommemorativeFocus, first responders]
-
A.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
B.
previouslyCommemoratedBy
Indicates that an entity was honored or remembered in the past through a specific commemorative act, object, or event.
-
C.
includesCommemoration
Indicates that one entity contains, incorporates, or features a commemoration of another entity, event, or person.
-
D.
commemorativeRelation
chosen
Indicates a relationship where one entity serves to honor, remember, or memorialize another entity, event, or person.
-
E.
hasCommemorativeStructure
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b542088190868531f84deaf9e4 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.