Triple
T20757171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LFSB |
E510878
|
entity |
| Predicate | distanceFromFreiburgKm |
P95329
|
FINISHED |
| Object | 46 |
—
|
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: 46 | Statement: [LFSB, distanceFromFreiburgKm, 46]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromFreiburgKm Context triple: [LFSB, distanceFromFreiburgKm, 46]
-
A.
distanceToFreiburgImBreisgau
chosen
Indicates the spatial distance between a given entity and the city of Freiburg im Breisgau.
-
B.
distanceToZurich_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Zurich.
-
C.
distanceToBern_km
Indicates the distance, measured in kilometers, between an entity’s location and the city of Bern.
-
D.
distanceToBasel_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Basel.
-
E.
distanceFromBuchsSG
Indicates the spatial distance measured from the reference location Buchs SG to another place or 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c23113c88190a567c3a098cf7552 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.