Triple
T26710983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topsham, Maine |
E673407
|
entity |
| Predicate | approximateDrivingTimeToPortland |
P89543
|
FINISHED |
| Object | about 30–40 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–40 minutes | Statement: [Topsham, Maine, approximateDrivingTimeToPortland, about 30–40 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDrivingTimeToPortland Context triple: [Topsham, Maine, approximateDrivingTimeToPortland, about 30–40 minutes]
-
A.
distanceToPortland
Indicates the measured distance between a given location and the city of Portland.
-
B.
approximateDrivingTime
chosen
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
-
C.
approximateDrivingTimeFromJuneau
Indicates the estimated amount of time it takes to drive from Juneau to another specified location.
-
D.
approximateDrivingTimeFromLAnse
Indicates the estimated amount of time it takes to drive from L'Anse to another specified location.
-
E.
approximateTripDuration
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 3:35 a.m.