Triple
T7658477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander Kelly Grayson |
E173443
|
entity |
| Predicate | commandHierarchy |
P11882
|
FINISHED |
| Object | second-in-command on the USS Orville |
—
|
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: second-in-command on the USS Orville | Statement: [Commander Kelly Grayson, commandHierarchy, second-in-command on the USS Orville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandHierarchy Context triple: [Commander Kelly Grayson, commandHierarchy, second-in-command on the USS Orville]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
-
D.
commandScope
Indicates that one entity defines or limits the range, context, or extent within which another entity’s command or control is valid or applicable.
-
E.
commandLevel
chosen
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:59 p.m.