Triple
T34481735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 54th Armored Infantry Battalion |
E885203
|
entity |
| Predicate | infantryType |
P6154
|
FINISHED |
| Object | armored 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: armored infantry | Statement: [54th Armored Infantry Battalion, infantryType, armored infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infantryType Context triple: [54th Armored Infantry Battalion, infantryType, armored infantry]
-
A.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
C.
garrisonOrCrewType
Indicates the specific kind of garrison or crew assigned to occupy, staff, or operate a given entity.
-
D.
garrisonForceType
Indicates the specific type or classification of military force assigned to occupy, defend, or maintain control of a particular location.
-
E.
garrisonType
Indicates the specific kind or classification of military garrison associated with an 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.