Triple
T29702705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göppingen |
E751532
|
entity |
| Predicate | distanceToStuttgart_km |
P49992
|
FINISHED |
| Object | approximately 40 |
—
|
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 40 | Statement: [Göppingen, distanceToStuttgart_km, approximately 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStuttgart_km Context triple: [Göppingen, distanceToStuttgart_km, approximately 40]
-
A.
distanceToStuttgart
chosen
Indicates the measured distance between a given entity’s location and the city of Stuttgart.
-
B.
distanceToKarlsruhe
Indicates the spatial distance between a given entity and the location of Karlsruhe.
-
C.
distanceToMunich
Indicates the spatial distance between a given entity’s location and the city of Munich.
-
D.
distanceToFrankfurt
Indicates the spatial distance between a given location or entity and the city of Frankfurt.
-
E.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00ab25c5b48190ad07ff508392ef56 |
completed | May 10, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_6a00a8a5cfc48190bbe97fb2bbd1b947 |
completed | May 10, 2026, 3:47 p.m. |
Created at: April 28, 2026, 7:25 p.m.