Triple
T33911525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Cairo |
E869326
|
entity |
| Predicate | connectsCapitalOfCountry |
P199324
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Paris–Cairo, connectsCapitalOfCountry, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCapitalOfCountry Context triple: [Paris–Cairo, connectsCapitalOfCountry, France]
-
A.
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.
-
B.
connectsCapitalCityOf
Indicates a relationship where something links or provides a direct connection to the capital city of a specified region, country, or administrative entity.
-
C.
linksCapitalOf
Indicates that one entity serves as the capital city of another entity, typically a country, state, or region.
-
D.
countryCapitalConnection
Indicates a relationship where a specific city serves as the official capital of a particular country.
-
E.
connectsCapitalCity
Indicates a relationship where an entity is linked or associated specifically with a capital 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: May 1, 2026, 1:48 a.m.