Triple
T29196931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoi–Tokyo |
E740150
|
entity |
| Predicate | destinationCapital |
P160390
|
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: [Hanoi–Tokyo, destinationCapital, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationCapital Context triple: [Hanoi–Tokyo, destinationCapital, Tokyo]
-
A.
destinationCapitalOf
chosen
Indicates that a location serves as the capital city of the specified destination or region.
-
B.
hostsCapitalOf
Indicates that one location serves as the capital city of another administrative or political entity.
-
C.
countryCapitalContext
Indicates that one entity serves as the capital city of the specified country in a given contextual or temporal setting.
-
D.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
E.
zoneCapital
Indicates that a given city or settlement serves as the capital of a specified administrative zone or region.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c23e6c81909bfcf620e519017a |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:04 p.m.