Triple
T21299979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorzów Wielkopolski |
E525032
|
entity |
| Predicate | co-capitalWith |
P87579
|
FINISHED |
| Object | Zielona Góra |
E149641
|
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: Zielona Góra | Statement: [Gorzów Wielkopolski, co-capitalWith, Zielona Góra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-capitalWith Context triple: [Gorzów Wielkopolski, co-capitalWith, Zielona Góra]
-
A.
hasCoCapital
chosen
Indicates that two or more cities share the status and functions of being capital cities of the same political or administrative entity.
-
B.
coversCapital
Indicates that one entity provides coverage, service, or applicability specifically to the capital city of another entity.
-
C.
isFinancialCapitalOf
Indicates that a city or region serves as the primary center for a country’s or area’s financial, banking, and economic market activities.
-
D.
secondaryCapital
Indicates that a location serves as an additional or secondary capital city for a political entity, alongside its primary capital.
-
E.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385b1c548190b940ded0163ee3ca |
completed | April 21, 2026, 8:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28e43934e88190adea7b10d2f72ca0 |
completed | June 10, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.