Triple
T30772552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudanese states |
E783565
|
entity |
| Predicate | haveCapital |
P204
|
FINISHED |
| Object | state capital city |
—
|
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: state capital city | Statement: [Sudanese states, haveCapital, state capital city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCapital Context triple: [Sudanese states, haveCapital, state capital city]
-
A.
hasCapital
chosen
Indicates that a place or political entity has a specific city designated as its capital.
-
B.
hasCoCapital
Indicates that two or more cities share the status and functions of being capital cities of the same political or administrative entity.
-
C.
hasCapitalFeature
Indicates that one entity possesses or is characterized by a primary or most important feature represented by the other entity.
-
D.
hasCapitalType
Indicates that a specified location’s capital is of a particular type (e.g., political, administrative, or economic capital).
-
E.
hasAssociatedCapital
Indicates that an entity is linked to a specific capital city that serves as its primary administrative or political center.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fc34b848190925e29fa4756f97d |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.