Triple
T25293173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakenham |
E634143
|
entity |
| Predicate | railLineNameSharedWith |
P28725
|
FINISHED |
| Object | Pakenham railway line |
—
|
NE NERFINISHED |
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: Pakenham railway line | Statement: [Pakenham, railLineNameSharedWith, Pakenham railway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railLineNameSharedWith Context triple: [Pakenham, railLineNameSharedWith, Pakenham railway line]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railLineOrigin
Indicates that a rail line begins or originates from a specified location or point.
-
C.
lineName
chosen
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
-
D.
railwayLineNow
Indicates that a previously existing railway line has been replaced, succeeded, or is currently represented by a new or different railway line.
-
E.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fcf4bc88190a9ffaa3b07d5b881 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.