Triple
T18048926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Mills |
E431874
|
entity |
| Predicate | distanceToDouglas |
P129612
|
FINISHED |
| Object | approximately 2.5 miles |
—
|
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 2.5 miles | Statement: [Union Mills, distanceToDouglas, approximately 2.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDouglas Context triple: [Union Mills, distanceToDouglas, approximately 2.5 miles]
-
A.
distanceFromPortDouglas
Indicates the measured distance between a given location and Port Douglas.
-
B.
distanceToDalhousie
Indicates the spatial distance between a given entity and Dalhousie.
-
C.
distanceToConcord
Indicates the spatial distance between an entity and the location named Concord.
-
D.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
E.
distanceToBellingham
Indicates the measured or estimated distance between a given entity’s location and the location of Bellingham.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff4a6e08190a5ca8d191aa7f0ae |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.