Triple
T17655885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point of Rocks, Maryland |
E429619
|
entity |
| Predicate | railwayStationStyle |
P128412
|
FINISHED |
| Object | Victorian Gothic |
—
|
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: Victorian Gothic | Statement: [Point of Rocks, Maryland, railwayStationStyle, Victorian Gothic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStationStyle Context triple: [Point of Rocks, Maryland, railwayStationStyle, Victorian Gothic]
-
A.
railwayStationCategory
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
B.
railwayStationInstanceOf
Indicates that a given railway station is an instance of a specified class or type of railway station.
-
C.
railStationManager
Indicates that one entity manages, operates, or is responsible for the administration of a particular railway station.
-
D.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
E.
railwayStationFunction
Indicates that an entity serves as a railway station and specifies the role or function it performs within the railway network.
- F. None of above. chosen
Provenance (4 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e40e344819086a49c69f8f2956b |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 6:06 a.m.