Triple
T2086860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McAuliffe Square |
E45370
|
entity |
| Predicate | hasDedicationReason |
P19091
|
FINISHED |
| Object | honoring U.S. General Anthony McAuliffe |
—
|
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: honoring U.S. General Anthony McAuliffe | Statement: [McAuliffe Square, hasDedicationReason, honoring U.S. General Anthony McAuliffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDedicationReason Context triple: [McAuliffe Square, hasDedicationReason, honoring U.S. General Anthony McAuliffe]
-
A.
dedicatee
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
B.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
dedicationDate
Indicates the date on which something (such as a building, monument, or work) is formally dedicated or inaugurated.
-
D.
designationReason
chosen
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
E.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba5641208190b925676b8d80f300 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.