Triple
T33429312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin–Rome route |
E856080
|
entity |
| Predicate | capitalToCapitalConnection |
P105217
|
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: [Berlin–Rome route, capitalToCapitalConnection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalToCapitalConnection Context triple: [Berlin–Rome route, capitalToCapitalConnection, true]
-
A.
countryCapitalConnection
Indicates a relationship where a specific city serves as the official capital of a particular country.
-
B.
hasCountryCapitalConnection
Indicates a relationship in which a specific country is associated with its official capital city.
-
C.
connectsCapitalsOf
chosen
Indicates a relationship where something serves as a link or route between the capital cities of two regions or countries.
-
D.
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.
-
E.
regionCapitalConnected
Indicates that a capital city is directly connected (e.g., by transport or infrastructure) to its surrounding 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 1:36 a.m.