Triple
T20234860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTH 101 |
E495622
|
entity |
| Predicate | bypassFunction |
P139338
|
FINISHED |
| Object | bypasses central Winnipeg |
—
|
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: bypasses central Winnipeg | Statement: [PTH 101, bypassFunction, bypasses central Winnipeg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bypassFunction Context triple: [PTH 101, bypassFunction, bypasses central Winnipeg]
-
A.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
B.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
C.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
D.
safetyFunction
Indicates that one entity serves as a safety-related function or mechanism that protects, safeguards, or reduces risk for another entity or process.
-
E.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716995b88190a8514b41232b0e94 |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.