Triple
T12925127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander (United States Navy rank) |
E309223
|
entity |
| Predicate | typicalResponsibilityLevel |
P11280
|
FINISHED |
| Object | unit command |
—
|
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 command | Statement: [Commander (United States Navy rank), typicalResponsibilityLevel, unit command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResponsibilityLevel Context triple: [Commander (United States Navy rank), typicalResponsibilityLevel, unit command]
-
A.
typicalSeniorityLevel
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
-
B.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
-
C.
typicalCommandLevel
chosen
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
D.
typicalLevelOfInfluence
Indicates the usual degree or strength of influence one entity exerts over another or within a given context.
-
E.
typicalCommitment
Indicates a standard or commonly expected level of obligation or promise that one entity holds toward another or toward performing an action.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971eb17c88190bf523da897172a0c |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.