Triple
T35607024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Mountains urban area |
E1028919
|
entity |
| Predicate | primaryRailway |
P109925
|
FINISHED |
| Object | Main Western line |
E68311
|
NE 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: Main Western line | Statement: [Blue Mountains urban area, primaryRailway, Main Western line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailway Context triple: [Blue Mountains urban area, primaryRailway, Main Western line]
-
A.
originalRailway
Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
-
B.
primaryRailUse
Indicates the main or predominant purpose for which a rail line, segment, or facility is used (e.g., passenger, freight, or mixed traffic).
-
C.
primaryRailLinkFor
chosen
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
D.
rail
Indicates that one entity criticizes, scolds, or complains vehemently about another entity or situation.
-
E.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
- F. None of above.
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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885ddaf64819080bf884b2e2d45c2 |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.