Triple
T33289901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudlersville Train Station Museum |
E852287
|
entity |
| Predicate | transportModeServedOriginally |
P169519
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Sudlersville Train Station Museum, transportModeServedOriginally, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeServedOriginally Context triple: [Sudlersville Train Station Museum, transportModeServedOriginally, rail]
-
A.
transportModeOriginal
chosen
Indicates the original mode of transportation used or intended for a given movement or trip before any changes or substitutions.
-
B.
servedByTransportation
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
-
C.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
D.
transportModeAfterConversion
Indicates the mode of transportation that results after a conversion or change from a previous transport mode.
-
E.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 1, 2026, 1:32 a.m.