Triple
T1156389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trzebinia |
E23791
|
entity |
| Predicate | voivodeshipCapitalDistance |
P15547
|
FINISHED |
| Object | approximately 35 km from Kraków |
—
|
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: approximately 35 km from Kraków | Statement: [Trzebinia, voivodeshipCapitalDistance, approximately 35 km from Kraków]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voivodeshipCapitalDistance Context triple: [Trzebinia, voivodeshipCapitalDistance, approximately 35 km from Kraków]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
distanceToKraków_km
chosen
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Kraków.
-
C.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
D.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
E.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc92ae008190a587c12ecc9a502a |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.