Triple
T30442435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo (Narita) – Okinawa (Naha) |
E774485
|
entity |
| Predicate | isNonstop |
P94244
|
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: [Tokyo (Narita) – Okinawa (Naha), isNonstop, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonstop Context triple: [Tokyo (Narita) – Okinawa (Naha), isNonstop, true]
-
A.
isNonStop
chosen
Indicates that a service, trip, or process occurs from start to finish without any intermediate stops or interruptions.
-
B.
isNonstopPossible
Indicates that it is possible to perform or complete the referenced trip, route, or process without any intermediate stops or interruptions.
-
C.
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.
-
D.
hasStops
Indicates that a route, service, or journey includes one or more intermediate stopping points at specified locations.
-
E.
isNonPeriodic
Indicates that the subject does not occur, repeat, or follow a pattern at regular intervals over time.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:08 p.m.