Triple
T6954595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xelayan |
E161209
|
entity |
| Predicate | travelCapability |
P74272
|
FINISHED |
| Object | faster-than-light space 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: faster-than-light space travel | Statement: [Xelayan, travelCapability, faster-than-light space travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelCapability Context triple: [Xelayan, travelCapability, faster-than-light space travel]
-
A.
travelFreedom
Indicates the degree to which an entity is allowed or able to move or travel freely across locations or jurisdictions without restriction.
-
B.
travelRequirement
Indicates that a certain amount or type of travel is necessary for participating in or fulfilling the associated activity, role, or arrangement.
-
C.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
D.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
E.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dace1a94819095311e4288f01784 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dacb524c81909aade2282a4c0c01 |
completed | March 27, 2026, 7:30 p.m. |
Created at: March 27, 2026, 2:29 p.m.