Triple
T35718633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Light Armored Reconnaissance Battalion |
E1032403
|
entity |
| Predicate | hasBattalionLevel |
P109891
|
FINISHED |
| Object | battalion |
—
|
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: battalion | Statement: [4th Light Armored Reconnaissance Battalion, hasBattalionLevel, battalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattalionLevel Context triple: [4th Light Armored Reconnaissance Battalion, hasBattalionLevel, battalion]
-
A.
hasBattalion
Indicates that one entity possesses, commands, or is organizationally assigned a specific battalion.
-
B.
hasBattalionStructure
chosen
Indicates that an entity is organized into or associated with a battalion-level military structure.
-
C.
isBattalionEquivalent
Indicates that one military unit has a size, role, or organizational status equivalent to that of a battalion.
-
D.
hasBattalionNumber
Indicates that an entity (such as a military unit) is associated with a specific battalion number identifier.
-
E.
hasBattalionType
Indicates that an entity (such as a military unit) is associated with or classified by a specific type of battalion.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:05 p.m.