Triple
T18215623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randolph/Wells |
E436146
|
entity |
| Predicate | servedTrainType |
P55099
|
FINISHED |
| Object | rapid transit |
—
|
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: rapid transit | Statement: [Randolph/Wells, servedTrainType, rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedTrainType Context triple: [Randolph/Wells, servedTrainType, rapid transit]
-
A.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
B.
railwayTypeServed
chosen
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
C.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
D.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
E.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e476a6548190bda03190c5f531ad |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.