Triple
T24358990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol–Weymouth line |
E614003
|
entity |
| Predicate | terminusCharacter |
P77353
|
FINISHED |
| Object | seaside town |
—
|
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: seaside town | Statement: [Bristol–Weymouth line, terminusCharacter, seaside town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCharacter Context triple: [Bristol–Weymouth line, terminusCharacter, seaside town]
-
A.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
B.
terminusFeature
chosen
Indicates that a specific physical or structural feature is located at, marks, or characterizes the endpoint or terminus of something.
-
C.
closingSectionCharacter
Indicates that one character functions as the closing or terminating symbol for a particular section or block of content in relation to another element.
-
D.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
E.
terminusUpper
Indicates that one entity serves as the upper or final endpoint (terminus) of another entity, such as a route, segment, or ordered structure.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2934bcc608190b86bc091474bb259 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.