Triple
T19110998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prionia trailhead |
E467786
|
entity |
| Predicate | approximateDrivingTimeFromLitochoro |
P89543
|
FINISHED |
| Object | about 30 minutes |
—
|
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: about 30 minutes | Statement: [Prionia trailhead, approximateDrivingTimeFromLitochoro, about 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDrivingTimeFromLitochoro Context triple: [Prionia trailhead, approximateDrivingTimeFromLitochoro, about 30 minutes]
-
A.
approximateDrivingTime
chosen
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
-
B.
approximateDrivingTimeFromLAnse
Indicates the estimated amount of time it takes to drive from L'Anse to another specified location.
-
C.
distanceToCraiova_km
Indicates the physical distance, measured in kilometers, between a given entity and the city of Craiova.
-
D.
distanceFromStaraZagoraApproximateKm
Indicates the approximate distance, measured in kilometers, between an entity and Stara Zagora.
-
E.
distanceToPlovdiv
Indicates the spatial distance between a given entity and the city of Plovdiv.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e393bafc81908e35a0eba7b807a6 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.