Triple
T36158767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungeness railway station |
E1045813
|
entity |
| Predicate | hasLineLengthFromHythe |
P39661
|
FINISHED |
| Object | approximately 13.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 13.5 miles | Statement: [Dungeness railway station, hasLineLengthFromHythe, approximately 13.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineLengthFromHythe Context triple: [Dungeness railway station, hasLineLengthFromHythe, approximately 13.5 miles]
-
A.
hasLineLength
chosen
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
-
B.
lineLengthType
Indicates the type or category used to characterize the length of a line.
-
C.
hasBaselineLength
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
-
D.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
E.
supportsLineLengthControl
Indicates that an entity provides functionality to configure or enforce limits on the length of lines (e.g., in text or code).
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:08 p.m.