Triple
T36789011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cibinium |
E909000
|
entity |
| Predicate | hasModernCountryCapital |
P185326
|
FINISHED |
| Object | Bucharest |
—
|
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: Bucharest | Statement: [Cibinium, hasModernCountryCapital, Bucharest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernCountryCapital Context triple: [Cibinium, hasModernCountryCapital, Bucharest]
-
A.
capitalFoundedModernCountry
Indicates that a capital city was established or founded by the modern country to which it currently belongs.
-
B.
hasCountryCapitalStatus
Indicates that a location holds the official status of being the capital city of a specified country.
-
C.
hasCountryCapitalSystem
Indicates a relationship where a country is associated with its capital city within a defined capital system or framework.
-
D.
capitalFoundedModernName
Indicates that the capital city was founded under a different historical name than the one it is known by in modern times.
-
E.
modernCountryOfCapital
chosen
Indicates that a given city serves as the capital of a specified modern-day country.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:12 p.m.