Triple
T22860855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldavia |
E566917
|
entity |
| Predicate | hasCapital |
P204
|
FINISHED |
| Object | Bârlad |
—
|
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: Bârlad | Statement: [Moldavia, hasCapital, Bârlad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bârlad Context triple: [Moldavia, hasCapital, Bârlad]
-
A.
Bârlad
chosen
Bârlad is a town in eastern Romania, historically part of the Moldavia region and known as a local cultural and educational center.
-
B.
Bacău
Bacău is a city in eastern Romania, serving as the administrative center of Bacău County and an important regional industrial and cultural hub in the historical region of Moldavia.
-
C.
Brăila
Brăila is a major port city on the Danube River in eastern Romania, known historically as an important commercial and industrial center.
-
D.
Râmnicu Vâlcea
Râmnicu Vâlcea is a city in south-central Romania, located on the Olt River and serving as the capital of Vâlcea County.
-
E.
Botoșani
Botoșani is a city in northeastern Romania known as a cultural and historical center of the Moldavia region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17efcc1308190a95d10e431295ca2 |
completed | April 29, 2026, 3:46 a.m. |
Created at: April 17, 2026, 3:37 p.m.