Triple
T14904369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevertire |
E360088
|
entity |
| Predicate | distanceFromDubbo_km |
P116605
|
FINISHED |
| Object | approximately 115 |
—
|
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 115 | Statement: [Nevertire, distanceFromDubbo_km, approximately 115]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDubbo_km Context triple: [Nevertire, distanceFromDubbo_km, approximately 115]
-
A.
distanceFromChengdu
Indicates the measured spatial distance between a given location and the city of Chengdu.
-
B.
distanceFromBeijing_km
Indicates the physical distance, measured in kilometers, between a given place or object and Beijing.
-
C.
distanceFromBratislava_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Bratislava.
-
D.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
E.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60cd5588190b1efecc2b220da69 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:12 a.m.