Triple
T25715421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Tokyo |
E644848
|
entity |
| Predicate | isNonstopServicePossible |
P60441
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [London–Tokyo, isNonstopServicePossible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonstopServicePossible Context triple: [London–Tokyo, isNonstopServicePossible, true]
-
A.
isNonstopPossible
chosen
Indicates that it is possible to perform or complete the referenced trip, route, or process without any intermediate stops or interruptions.
-
B.
isNonStop
Indicates that a service, trip, or process occurs from start to finish without any intermediate stops or interruptions.
-
C.
canStopService
Indicates that an entity has the authority or capability to terminate or halt a particular service.
-
D.
hasStopFeature
Indicates that one entity possesses or is equipped with a feature that enables stopping or halting an associated process, action, or movement.
-
E.
servedNonstopBy
Indicates that there is a direct, uninterrupted service (e.g., a route or connection) operating between two entities without any intermediate stops or transfers.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 9:40 p.m.