Triple
T22638412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 140th New York Infantry monument |
E558746
|
entity |
| Predicate | honorsSide |
P2354
|
FINISHED |
| Object | Union |
—
|
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: Union | Statement: [140th New York Infantry monument, honorsSide, Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsSide Context triple: [140th New York Infantry monument, honorsSide, Union]
-
A.
honors
chosen
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
B.
honorsSchool
Indicates that a school has received recognition, distinction, or special status for high achievement or excellence.
-
C.
honorsAspectOf
Indicates that one entity shows respect, recognition, or reverence specifically toward a particular aspect, quality, or facet of another entity.
-
D.
honorsRole
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
E.
honorsActivity
Indicates that one entity formally recognizes, celebrates, or pays tribute to an activity or action performed by another entity.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1700f9fac8190b82190a54be22413 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:04 p.m.