Triple
T10439876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caisson Platoon |
E246139
|
entity |
| Predicate | honorsRenderedFor |
P2354
|
FINISHED |
| Object | members of the U.S. Armed Forces |
—
|
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: members of the U.S. Armed Forces | Statement: [Caisson Platoon, honorsRenderedFor, members of the U.S. Armed Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsRenderedFor Context triple: [Caisson Platoon, honorsRenderedFor, members of the U.S. Armed Forces]
-
A.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
B.
honors
chosen
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
C.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
D.
honorsNumber
Indicates that one entity formally recognizes or commemorates another by assigning or associating a specific number with it.
-
E.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:15 p.m.