Triple
T37027835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savez komunista Hrvatske |
E916404
|
entity |
| Predicate | governedFromCapital |
P151561
|
FINISHED |
| Object | Zagreb |
E31635
|
NE 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: Zagreb | Statement: [Savez komunista Hrvatske, governedFromCapital, Zagreb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedFromCapital Context triple: [Savez komunista Hrvatske, governedFromCapital, Zagreb]
-
A.
capitalCityGoverningFrom
chosen
Indicates that a specified capital city serves as the administrative center from which a given political entity is governed.
-
B.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
C.
capitalCityGoverned
Indicates that a particular capital city is under the administrative or political authority of a specified governing body or jurisdiction.
-
D.
governingCountryCapitalLocatedIn
Indicates that the capital city of a governing country is geographically located within a specified territory or region.
-
E.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
- F. None of above.
Provenance (4 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a03232efd8481908ee25447a29ee20b |
completed | May 12, 2026, 12:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e576ecbb8819088c982b3775b7524 |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a032269dcb08190907c965c28145b77 |
completed | May 12, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:14 p.m.