Triple
T28632980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka–Tokyo Haneda |
E724694
|
entity |
| Predicate | cityAtOtherEnd |
P165527
|
FINISHED |
| Object | Tokyo |
—
|
NE NERFINISHED |
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: Tokyo | Statement: [Fukuoka–Tokyo Haneda, cityAtOtherEnd, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAtOtherEnd Context triple: [Fukuoka–Tokyo Haneda, cityAtOtherEnd, Tokyo]
-
A.
primaryCityAtOtherEnd
Indicates that a given city is the main or principal city located at the opposite end of a specified route, connection, or relationship from another city.
-
B.
otherCity
Indicates that one city is different from and not the same as another city.
-
C.
destinationCity
Indicates the city to which an entity is traveling, being sent, or ultimately directed.
-
D.
city1
Indicates that the subject is classified as a city.
-
E.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 4:38 a.m.