Triple
T28859851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revalia |
E728827
|
entity |
| Predicate | associatedWithCapitalStatus |
P199583
|
FINISHED |
| Object | capital city of Estonia |
—
|
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: capital city of Estonia | Statement: [Revalia, associatedWithCapitalStatus, capital city of Estonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCapitalStatus Context triple: [Revalia, associatedWithCapitalStatus, capital city of Estonia]
-
A.
hasAssociatedCapital
Indicates that an entity is linked to a specific capital city that serves as its primary administrative or political center.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
currentCapitalStatus
chosen
Indicates whether a given location currently holds the official status of capital (e.g., of a country, state, or region).
-
D.
earlierCapitalAssociated
Indicates that one entity served as a capital city at an earlier time than the other associated capital entity.
-
E.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: April 28, 2026, 6:46 a.m.