Triple
T2086846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McAuliffe Square |
E45370
|
entity |
| Predicate | hasSubjectOfMemorial |
P500
|
FINISHED |
| Object | U.S. forces in the Battle of the Bulge |
—
|
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: U.S. forces in the Battle of the Bulge | Statement: [McAuliffe Square, hasSubjectOfMemorial, U.S. forces in the Battle of the Bulge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectOfMemorial Context triple: [McAuliffe Square, hasSubjectOfMemorial, U.S. forces in the Battle of the Bulge]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
commemoratedBy
chosen
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
C.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
memorialName
Indicates that a memorial is known by or designated with a particular name.
-
E.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
- 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.