Triple
T29119982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayshell sector |
E737151
|
entity |
| Predicate | travelAccess |
P100062
|
FINISHED |
| Object | reachable by hyperspace travel |
—
|
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: reachable by hyperspace travel | Statement: [Sayshell sector, travelAccess, reachable by hyperspace travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelAccess Context triple: [Sayshell sector, travelAccess, reachable by hyperspace travel]
-
A.
travelMechanic
chosen
Indicates the method or system by which movement or travel between locations is carried out.
-
B.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
C.
connectsTravelBetween
Indicates a relationship where something (such as a route, service, or mode of transport) enables or provides travel between two locations.
-
D.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
E.
travelRequirement
Indicates that a certain amount or type of travel is necessary for participating in or fulfilling the associated activity, role, or arrangement.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 11:25 a.m.