Triple
T16396804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lima Company, 3rd Battalion, 1st Marines |
E398203
|
entity |
| Predicate | combatArmCategory |
P33638
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Lima Company, 3rd Battalion, 1st Marines, combatArmCategory, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatArmCategory Context triple: [Lima Company, 3rd Battalion, 1st Marines, combatArmCategory, infantry]
-
A.
combatArm
chosen
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
B.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
C.
weaponCategory
Indicates the classification or type of weapon to which an item or armament belongs.
-
D.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
-
E.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cb3c708190b64341cb1410ed81 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.