Triple
T7119870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HS1 Ltd |
E165920
|
entity |
| Predicate | hasLineType |
P48760
|
FINISHED |
| Object | passenger 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: passenger rail | Statement: [HS1 Ltd, hasLineType, passenger rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineType Context triple: [HS1 Ltd, hasLineType, passenger rail]
-
A.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
B.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
C.
servedLineType
chosen
Indicates the type or category of service line associated with or provided in a given context.
-
D.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
E.
hasLineElementForm
Indicates that something takes the form or representation of a line element within a given structure or context.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61ca6a88190a0eb9f287e3b723c |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.