Triple
T2127147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant (USSF enlisted rank) |
E46452
|
entity |
| Predicate | commandResponsibilityLevel |
P11280
|
FINISHED |
| Object | tactical |
—
|
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: tactical | Statement: [Sergeant (USSF enlisted rank), commandResponsibilityLevel, tactical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandResponsibilityLevel Context triple: [Sergeant (USSF enlisted rank), commandResponsibilityLevel, tactical]
-
A.
commandLevel
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
-
B.
typicalCommandLevel
chosen
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
C.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
D.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
E.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb75033881909b16659fc73945ef |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.