Triple
T38296767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Africa/Cairo |
E1032108
|
entity |
| Predicate | capitalCityOfObservedCountry |
P38097
|
FINISHED |
| Object | Cairo |
—
|
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: Cairo | Statement: [Africa/Cairo, capitalCityOfObservedCountry, Cairo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityOfObservedCountry Context triple: [Africa/Cairo, capitalCityOfObservedCountry, Cairo]
-
A.
capitalCityOfCountry
Indicates that a city serves as the official capital of a specified country.
-
B.
capitalCityObservedIn
chosen
Indicates that a particular capital city was observed, recorded, or identified within a specified context, location, or time frame.
-
C.
capitalOfGoverningCountry
Indicates that a city serves as the capital of the country that governs a given territory or region.
-
D.
destinationCapitalOf
Indicates that a location serves as the capital city of the specified destination or region.
-
E.
capitalOfType
Indicates that one entity serves as the capital city (or administrative capital) of a specified type of political or administrative unit represented by the other entity.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:30 p.m.