Triple
T34404449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Company B, 1st Battalion, 121st Infantry Regiment |
E883070
|
entity |
| Predicate | natoCommandStructureLevel |
P18686
|
FINISHED |
| Object | company |
—
|
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: company | Statement: [Company B, 1st Battalion, 121st Infantry Regiment, natoCommandStructureLevel, company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natoCommandStructureLevel Context triple: [Company B, 1st Battalion, 121st Infantry Regiment, natoCommandStructureLevel, company]
-
A.
militaryFormationLevel
chosen
Indicates the hierarchical level or scale of a military formation within an armed forces organizational structure.
-
B.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
C.
roleInNATO
Indicates the specific capacity, position, or function an entity holds within the organizational or operational structure of NATO.
-
D.
NATOStandard
Indicates that something conforms to, is defined by, or is governed by standards established by NATO.
-
E.
associatedWithNATO
Indicates a relationship in which an entity has a formal or recognized connection, affiliation, or involvement with NATO.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.