Triple
T25074292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julijska krajina |
E628003
|
entity |
| Predicate | hasCapitalCityHistorically |
P98392
|
FINISHED |
| Object | Trieste |
—
|
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: Trieste | Statement: [Julijska krajina, hasCapitalCityHistorically, Trieste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalCityHistorically Context triple: [Julijska krajina, hasCapitalCityHistorically, Trieste]
-
A.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
B.
capitalOrMajorCityHistorically
chosen
Indicates that a place has historically served as a capital or as a major, centrally important city for a political or cultural entity.
-
C.
formerCapitalOf
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
D.
hasHistoricCapitolBuilding
Indicates that an entity possesses or is associated with a building that historically served as a capitol or seat of government.
-
E.
hasTraditionalCapital
Indicates that an entity serves or is recognized as the traditional or historical capital 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:20 a.m.