Triple
T14565857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto north–south rapid transit corridor |
E341782
|
entity |
| Predicate | expectedUsers |
P22398
|
FINISHED |
| Object | commuters |
—
|
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: commuters | Statement: [Toronto north–south rapid transit corridor, expectedUsers, commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedUsers Context triple: [Toronto north–south rapid transit corridor, expectedUsers, commuters]
-
A.
userCount
chosen
Indicates the number of users associated with or involved in a given context or entity.
-
B.
intendedPlayers
Indicates the players for whom something (such as a game, item, or activity) is designed or meant to be used.
-
C.
expectedNumberOfAthletes
Indicates the anticipated or planned count of athletes expected to participate in a given context or event.
-
D.
otherUsers
Indicates a relationship where one or more users are distinguished as being different from a given primary or reference user.
-
E.
requiresPlayers
Indicates that one entity needs a certain number or set of players to participate, function, or be valid.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38c6350819091090ffd15772f6f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.