Triple
T17498778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennett, British Columbia |
E426140
|
entity |
| Predicate | transportModeHistorical |
P127684
|
FINISHED |
| Object | railway |
—
|
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: railway | Statement: [Bennett, British Columbia, transportModeHistorical, railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeHistorical Context triple: [Bennett, British Columbia, transportModeHistorical, railway]
-
A.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
B.
historicalTraction
Indicates that the subject has demonstrated sustained relevance, influence, or effectiveness over a significant period of time.
-
C.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
D.
hasTramHistory
Indicates that there exists a historical association or record of tram-related activity or infrastructure involving the subject.
-
E.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4521028048190aa7c4023a72a12f4 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.