Triple
T13646165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surrey Iron Railway |
E326106
|
entity |
| Predicate | railForm |
P110960
|
FINISHED |
| Object | L-shaped plate rails |
—
|
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: L-shaped plate rails | Statement: [Surrey Iron Railway, railForm, L-shaped plate rails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railForm Context triple: [Surrey Iron Railway, railForm, L-shaped plate rails]
-
A.
railComponent
Indicates a relationship where one entity is a structural or functional part of a rail or railway system component of another entity.
-
B.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
-
C.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
-
D.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
E.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:51 p.m.