Triple
T28749967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Marine Corps Ground Combat Element |
E731491
|
entity |
| Predicate | usesCombatArm |
P73205
|
FINISHED |
| Object | infantry units |
—
|
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 units | Statement: [United States Marine Corps Ground Combat Element, usesCombatArm, infantry units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCombatArm Context triple: [United States Marine Corps Ground Combat Element, usesCombatArm, infantry units]
-
A.
combatArm
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.
usesCombatSystem
chosen
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
C.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
D.
isCombatUnit
Indicates that an entity functions as a unit specifically designated and equipped to engage in combat operations.
-
E.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 6:07 a.m.