Triple
T7690840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin–Westport railway line (branch to Ballina) |
E174239
|
entity |
| Predicate | lineCategory |
P76380
|
FINISHED |
| Object | secondary rail route |
—
|
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: secondary rail route | Statement: [Dublin–Westport railway line (branch to Ballina), lineCategory, secondary rail route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineCategory Context triple: [Dublin–Westport railway line (branch to Ballina), lineCategory, secondary rail route]
-
A.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
C.
lineSymbol
Indicates that one entity is used as a line-style or line-representation symbol for another entity.
-
D.
lineName
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
-
E.
lineUse
chosen
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.