Triple
T12479304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brill |
E298261
|
entity |
| Predicate | servedByRailwayBranchType |
P58624
|
FINISHED |
| Object | remote branch line |
—
|
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: remote branch line | Statement: [Brill, servedByRailwayBranchType, remote branch line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByRailwayBranchType Context triple: [Brill, servedByRailwayBranchType, remote branch line]
-
A.
servedByRailBranch
chosen
Indicates that a location or facility is connected to and provided service by a specific railway branch line.
-
B.
railwayTypeServed
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.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
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.
railwayName
Indicates the name assigned to a specific railway or railway line in the relationship.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.