Triple
T32288946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | division support group |
E824911
|
entity |
| Predicate | operatesAtEchelon |
P86605
|
FINISHED |
| Object | division level |
—
|
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: division level | Statement: [division support group, operatesAtEchelon, division level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAtEchelon Context triple: [division support group, operatesAtEchelon, division level]
-
A.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
B.
worksAtLevel
chosen
Indicates that an entity performs work or holds a role at a specified hierarchical or organizational level.
-
C.
operatedOnLevel
Indicates that an action or process was performed at, or with respect to, a specific level or layer within a system or structure.
-
D.
operatesAtHigh
Indicates that an entity functions or performs its activity at a high level, intensity, capacity, or setting relative to a defined scale or standard.
-
E.
echelon
Indicates a hierarchical arrangement where entities are organized into levels or ranks, often with each level subordinate to the one above it.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
Created at: May 1, 2026, 12:44 a.m.