Triple
T8454921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sveta Nedelja, Croatia |
E199895
|
entity |
| Predicate | distanceToInKilometers |
P22795
|
FINISHED |
| Object | approximately 15 |
—
|
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 15 | Statement: [Sveta Nedelja, Croatia, distanceToInKilometers, approximately 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToInKilometers Context triple: [Sveta Nedelja, Croatia, distanceToInKilometers, approximately 15]
-
A.
approximateDistanceKm
chosen
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
B.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
C.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
D.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
E.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48ca9988190b60ebd09a135194d |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.