Triple
T28176310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Bucharest–Ploiești area |
E715598
|
entity |
| Predicate | BucharestIsCapitalOf |
P90792
|
FINISHED |
| Object | Romania |
—
|
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: Romania | Statement: [Greater Bucharest–Ploiești area, BucharestIsCapitalOf, Romania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BucharestIsCapitalOf Context triple: [Greater Bucharest–Ploiești area, BucharestIsCapitalOf, Romania]
-
A.
capitalOfIncludedCountry
Indicates that a city serves as the capital of a country that is included within a specified larger geopolitical or organizational entity.
-
B.
timeInCapital
Indicates that a specified amount of time is spent or occurs within the capital city of a given political or administrative entity.
-
C.
basedInCapital
Indicates that an entity is located or has its main base of operations in a capital city.
-
D.
regionalOrganizationCapital
Indicates that a city serves as the capital or administrative center of a specified regional organization.
-
E.
hostCountryCapitalCity
chosen
Indicates that a given city serves as the capital of a specified host 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6423b561c819088edf7b1cd739d75 |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:16 p.m.