Triple
T35442709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leros–Athens |
E1024393
|
entity |
| Predicate | connectsIslandToCapital |
P200418
|
FINISHED |
| Object | Leros |
—
|
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: Leros | Statement: [Leros–Athens, connectsIslandToCapital, Leros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsIslandToCapital Context triple: [Leros–Athens, connectsIslandToCapital, Leros]
-
A.
regionCapitalConnected
Indicates that a capital city is directly connected (e.g., by transport or infrastructure) to its surrounding region.
-
B.
connectsCapitalsOf
Indicates a relationship where something serves as a link or route between the capital cities of two regions or countries.
-
C.
connectsCountryCapitalToCity
Indicates a relationship that links a country’s capital to a specific city associated with that country.
-
D.
hasCountryCapitalConnection
Indicates a relationship in which a specific country is associated with its official capital city.
-
E.
connectsCapitalOf
Indicates a relationship where one entity serves as the capital city of another entity, linking the capital to the political or administrative unit it represents.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
| PDg | Predicate description generation | batch_69ff891d54248190be8742197564605a |
completed | May 9, 2026, 7:21 p.m. |
Created at: May 3, 2026, 4:04 p.m.