Triple
T3660158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyber-Planner |
E77627
|
entity |
| Predicate | commandHierarchyPosition |
P43225
|
FINISHED |
| Object | top of Cyberman command structure |
—
|
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: top of Cyberman command structure | Statement: [Cyber-Planner, commandHierarchyPosition, top of Cyberman command structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandHierarchyPosition Context triple: [Cyber-Planner, commandHierarchyPosition, top of Cyberman command structure]
-
A.
positionInHierarchy
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
B.
orderHierarchy
chosen
Indicates a hierarchical ordering relationship where one entity is positioned above or below another in a structured sequence or chain of command.
-
C.
commandLevel
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
-
D.
positionInCascade
Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
-
E.
branchPosition
Indicates the relative location or placement of something along a branch.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d5e5f881909c7c105827d41071 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.