Triple
T30093098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darfield |
E764787
|
entity |
| Predicate | servedHistoricallyBy |
P19592
|
FINISHED |
| Object | Dearne Valley railway |
—
|
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: Dearne Valley railway | Statement: [Darfield, servedHistoricallyBy, Dearne Valley railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedHistoricallyBy Context triple: [Darfield, servedHistoricallyBy, Dearne Valley railway]
-
A.
historicallyServedBy
chosen
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
B.
servedBefore
Indicates that one entity was served prior to another in time or sequence.
-
C.
originallyServes
Indicates that an entity was initially intended or designated to serve, function for, or be used by another entity or purpose.
-
D.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 29, 2026, 7:06 p.m.