Triple
T29613767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitfist turret |
E754802
|
entity |
| Predicate | hasTraverse |
P195899
|
FINISHED |
| Object | 360-degree |
—
|
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: 360-degree | Statement: [Hitfist turret, hasTraverse, 360-degree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraverse Context triple: [Hitfist turret, hasTraverse, 360-degree]
-
A.
usesTraversal
Indicates that one entity performs or relies on a traversal process or path to interact with, reach, or operate on another entity.
-
B.
alsoTraverses
Indicates that a route, path, or entity passes through or crosses an additional location or segment beyond its primary traversal.
-
C.
hasEdgeTraversal
Indicates that one entity moves along, crosses, or otherwise traverses an edge or connection between nodes in a graph or network.
-
D.
enablesTraversal
Indicates that one entity provides the means or capability for another entity to move through, across, or along something.
-
E.
requiresTraversalDirection
Indicates that a relationship or process can only be correctly followed or applied when moving through a structure in a specified direction.
- F. None of above. chosen
Provenance (4 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69fdee75d1408190bba58a9cef200a54 |
completed | May 8, 2026, 2:08 p.m. |
Created at: April 28, 2026, 6:30 p.m.