Triple
T15507313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 69th Tank Battalion |
E379115
|
entity |
| Predicate | militaryForm |
P118922
|
FINISHED |
| Object | armored unit |
—
|
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 unit | Statement: [69th Tank Battalion, militaryForm, armored unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryForm Context triple: [69th Tank Battalion, militaryForm, armored unit]
-
A.
militaryFormationOf
Indicates that one entity is a military unit or formation that is organizationally part of, or derived from, another entity.
-
B.
usedMilitaryFormation
Indicates that an entity employed a specific military formation or tactical arrangement of forces in a military context.
-
C.
militaryProvision
Indicates the provision, allocation, or supply of military resources, services, or support from one entity to another.
-
D.
militaryFormationNumber
Indicates the specific numerical designation assigned to a military formation within an armed force.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcea8888190a7b69aca360183c3 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:55 a.m.