Triple
T20722355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 28 |
E509348
|
entity |
| Predicate | hasRailwayCharacter |
P108254
|
FINISHED |
| Object | suburban railway |
—
|
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: suburban railway | Statement: [Line 28, hasRailwayCharacter, suburban railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayCharacter Context triple: [Line 28, hasRailwayCharacter, suburban railway]
-
A.
railwayCharacter
chosen
Indicates a relationship where an entity is characterized or defined as a railway-related figure, role, or persona.
-
B.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
C.
hasRailwayTraction
Indicates that a railway system, line, or vehicle uses a specified type or method of traction (e.g., electric, diesel, steam) for its propulsion.
-
D.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
E.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d6bdcc8190ba42c44159a2c0d5 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:27 p.m.