Triple
T33093858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Sergeant Major (USA) |
E846854
|
entity |
| Predicate | reports to |
P94491
|
FINISHED |
| Object | unit commander |
—
|
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: unit commander | Statement: [Command Sergeant Major (USA), reports to, unit commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reports to Context triple: [Command Sergeant Major (USA), reports to, unit commander]
-
A.
reportsFor
chosen
Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
-
B.
reportsAs
Indicates that one entity formally reports information, status, or results to another entity.
-
C.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
D.
reportsInformallyTo
Indicates that one person regularly provides updates or seeks guidance from another in a non-official, non-hierarchical reporting relationship.
-
E.
reportsSymbolicallyTo
Indicates that one entity formally reports to another through symbolic, representational, or non-literal means rather than through direct, operational authority.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.