Triple
T37305570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifle Company A |
E926068
|
entity |
| Predicate | garrisonService |
P187721
|
FINISHED |
| Object | United States Marine Corps |
—
|
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: United States Marine Corps | Statement: [Rifle Company A, garrisonService, United States Marine Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonService Context triple: [Rifle Company A, garrisonService, United States Marine Corps]
-
A.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
-
B.
garrisonCommand
Indicates that one entity holds command authority over the garrison or stationed military forces at a particular location.
-
C.
garrisonState
Indicates that a military force is stationed in or assigned to defend a particular state or territory.
-
D.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
E.
garrisonLabel
Indicates the designation or identifying label assigned to a military garrison associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:16 p.m.