Triple
T16046468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSL 4 |
E389232
|
entity |
| Predicate | railwayLineNumberingSystem |
P121745
|
FINISHED |
| Object | Belgian railway line numbering |
—
|
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: Belgian railway line numbering | Statement: [HSL 4, railwayLineNumberingSystem, Belgian railway line numbering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineNumberingSystem Context triple: [HSL 4, railwayLineNumberingSystem, Belgian railway line numbering]
-
A.
hasRailwayStationNumberingSystem
Indicates that a railway station is associated with a specific system for assigning it an identifying number or code.
-
B.
railwayLineNumber
Indicates the identifying number assigned to a specific railway line within a rail network.
-
C.
hasRailwayLineNumber
Indicates the specific identification number assigned to a railway line associated with an entity.
-
D.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
E.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:56 a.m.