Triple
T35386990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp Whistle |
E1022815
|
entity |
| Predicate | hasWarpDestination |
P83648
|
FINISHED |
| Object | World 2 |
—
|
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: World 2 | Statement: [Warp Whistle, hasWarpDestination, World 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarpDestination Context triple: [Warp Whistle, hasWarpDestination, World 2]
-
A.
hasWarp
Indicates that one entity possesses, is equipped with, or is capable of using a warp or warp-related mechanism in relation to another entity or context.
-
B.
hasPlayerDestination
Indicates that a player entity is associated with, or is intended to move toward, a specific destination location or target.
-
C.
hasWarpFactor
Indicates the warp speed level or factor at which an entity (typically a spacecraft) is traveling or operating.
-
D.
hasDestinationRegion
chosen
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
E.
hasMainDestination
Indicates that an entity is primarily intended to go to, serve, or be directed toward a particular destination.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:03 p.m.