Triple
T38568691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifle Company C |
E928299
|
entity |
| Predicate | garrisonUnitOf |
P123262
|
FINISHED |
| Object | 1st Battalion, 8th Marines |
—
|
NE NERFINISHED |
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: 1st Battalion, 8th Marines | Statement: [Rifle Company C, garrisonUnitOf, 1st Battalion, 8th Marines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonUnitOf Context triple: [Rifle Company C, garrisonUnitOf, 1st Battalion, 8th Marines]
-
A.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
B.
garrisonParentUnit
chosen
Indicates that a military unit serves as the parent or higher-level command for a garrisoned subordinate unit.
-
C.
garrisonOfParentUnit
Indicates that a unit is stationed at or based in the same garrison location as its parent (higher-level) military unit.
-
D.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
E.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.