Triple
T13979741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox Company, 2nd Battalion, 4th Marines |
E336275
|
entity |
| Predicate | standardCommandLanguage |
P6537
|
FINISHED |
| Object | US military terminology |
—
|
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: US military terminology | Statement: [Fox Company, 2nd Battalion, 4th Marines, standardCommandLanguage, US military terminology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCommandLanguage Context triple: [Fox Company, 2nd Battalion, 4th Marines, standardCommandLanguage, US military terminology]
-
A.
languageOfCommand
chosen
Indicates that a specified language is the one in which a given command is expressed or issued.
-
B.
commandSyntax
Indicates the specific structure or format in which a command must be written or expressed.
-
C.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
-
D.
procedureLanguage
Indicates the programming or formal language in which a given procedure, method, or algorithm is expressed or implemented.
-
E.
procedureLanguageChoice
Indicates that a specific programming or scripting language is selected or used to implement or define a given procedure.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea10dc88190b9720919a021e570 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.