Triple
T25305696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newmarket Railway |
E634475
|
entity |
| Predicate | operatedRailwayLines |
P70721
|
FINISHED |
| Object | lines serving Newmarket |
—
|
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: lines serving Newmarket | Statement: [Newmarket Railway, operatedRailwayLines, lines serving Newmarket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRailwayLines Context triple: [Newmarket Railway, operatedRailwayLines, lines serving Newmarket]
-
A.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
B.
operatesRailLinesOnIsland
Indicates that a railway operator runs or manages rail lines located on a specific island.
-
C.
operatedOnRailroad
Indicates that an entity conducted operations or provided services on a railroad system.
-
D.
operatedRoutes
chosen
Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
-
E.
servedRailroadsIn
Indicates that an individual or entity provided service or worked in an official capacity for one or more specified railroad companies.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 21, 2026, 1:25 p.m.