Triple
T37930815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlow Branch Line |
E946210
|
entity |
| Predicate | endOnConnection |
P48547
|
FINISHED |
| Object | Great Western Main Line at Maidenhead |
—
|
NE NERFINISHED |
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: Great Western Main Line at Maidenhead | Statement: [Marlow Branch Line, endOnConnection, Great Western Main Line at Maidenhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOnConnection Context triple: [Marlow Branch Line, endOnConnection, Great Western Main Line at Maidenhead]
-
A.
canEndOn
Indicates that one entity is allowed or able to terminate, conclude, or finish with another specified entity or condition.
-
B.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
D.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
E.
connectionTerminationMethod
Indicates the method or process by which a connection between entities is ended or terminated.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.