Triple
T30777978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobingen |
E783728
|
entity |
| Predicate | distanceToAugsburg_km |
P203290
|
FINISHED |
| Object | approximately 13 |
—
|
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 13 | Statement: [Bobingen, distanceToAugsburg_km, approximately 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAugsburg_km Context triple: [Bobingen, distanceToAugsburg_km, approximately 13]
-
A.
distanceToMunich
Indicates the spatial distance between a given entity’s location and the city of Munich.
-
B.
distanceToPassau
Indicates the spatial distance between a given entity or location and the city of Passau.
-
C.
distanceToWuerzburg
Indicates the spatial distance between a given location or entity and the city of Würzburg.
-
D.
distanceToEisenstadt_km
Indicates the physical distance, measured in kilometers, between a given place and Eisenstadt.
-
E.
distanceToRosenheim
Indicates the spatial distance between a given entity and the location Rosenheim.
- F. None of above. chosen
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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a014a0b57dc8190b04ce51156ab95fa |
completed | May 11, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0149afa57c8190a83257085766d916 |
completed | May 11, 2026, 3:14 a.m. |
| PDg | Predicate description generation | batch_6a014a0ab56c819082ce383fb5987654 |
completed | May 11, 2026, 3:16 a.m. |
Created at: April 29, 2026, 8:41 p.m.