Triple
T13784459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC single fare zone |
E331216
|
entity |
| Predicate | governsPaymentWithin |
P104947
|
FINISHED |
| Object | City of Toronto municipal boundary |
—
|
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: City of Toronto municipal boundary | Statement: [TTC single fare zone, governsPaymentWithin, City of Toronto municipal boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPaymentWithin Context triple: [TTC single fare zone, governsPaymentWithin, City of Toronto municipal boundary]
-
A.
canBePaidTo
Indicates that one entity is allowed or able to transfer payment to another entity.
-
B.
payableIn
Indicates that a specified amount, obligation, or transaction must be settled using a particular currency, asset, or payment medium.
-
C.
conditionForPayment
Indicates the specific requirement or situation that must be satisfied before a payment is made.
-
D.
governsAfter
Indicates that one entity assumes governing authority or control after another entity’s period of governance has ended.
-
E.
paymentNetworkScope
chosen
Indicates the extent or domain within which a payment network operates or is considered applicable in the relationship.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.