Triple
T22648410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinnor and Princes Risborough Railway |
E559026
|
entity |
| Predicate | heritageLineLengthApprox |
P149055
|
FINISHED |
| Object | about 4 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: about 4 miles | Statement: [Chinnor and Princes Risborough Railway, heritageLineLengthApprox, about 4 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageLineLengthApprox Context triple: [Chinnor and Princes Risborough Railway, heritageLineLengthApprox, about 4 miles]
-
A.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
-
C.
historicalLength
Indicates the duration or extent of time over which something has existed, occurred, or been recorded in the past.
-
D.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
E.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17039c2bc8190972a7c169b27005c |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:05 p.m.