Triple
T29151977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoi–Frankfurt |
E738934
|
entity |
| Predicate | continentToContinent |
P180429
|
FINISHED |
| Object | Asia–Europe |
—
|
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: Asia–Europe | Statement: [Hanoi–Frankfurt, continentToContinent, Asia–Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentToContinent Context triple: [Hanoi–Frankfurt, continentToContinent, Asia–Europe]
-
A.
continentOfCountry
Indicates that a given continent is the one on which a specified country is geographically located.
-
B.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
-
C.
alsoContinent
Indicates that two entities share the same continent or that one entity is located on a continent in addition to another.
-
D.
continentOfLocation
Indicates that one entity is the continent on which the other entity is geographically located.
-
E.
continentB
Indicates that the subject entity is a continent that contains or is associated with the object entity (such as a country, region, or location).
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 28, 2026, 11:42 a.m.