Triple
T33600566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaudesert |
E860704
|
entity |
| Predicate | formerRailwayTerminusOf |
P151408
|
FINISHED |
| Object | Beaudesert railway line |
—
|
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: Beaudesert railway line | Statement: [Beaudesert, formerRailwayTerminusOf, Beaudesert railway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRailwayTerminusOf Context triple: [Beaudesert, formerRailwayTerminusOf, Beaudesert railway line]
-
A.
formerRailwayStation
Indicates that a location previously functioned as a railway station but is no longer in active railway service.
-
B.
servedByRailwayTerminus
Indicates that a place or location is provided rail transport services by a specific railway terminus.
-
C.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
D.
railTerminusFor
chosen
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
-
E.
foundedAsRailroadStopFor
Indicates that one place or settlement was originally established specifically to serve as a railroad stop for another location or line.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 1, 2026, 1:41 a.m.