Triple
T7702182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 501 Queen |
E174524
|
entity |
| Predicate | operatedByAgencyType |
P49812
|
FINISHED |
| Object | municipal transit agency |
—
|
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: municipal transit agency | Statement: [501 Queen, operatedByAgencyType, municipal transit agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByAgencyType Context triple: [501 Queen, operatedByAgencyType, municipal transit agency]
-
A.
agencyTypeOfOperator
chosen
Indicates the specific type or category of agency to which the operator belongs or by which the operator is characterized.
-
B.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
D.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
E.
operatedByBranch
Indicates that an entity is run, managed, or controlled by a specific branch of an organization.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.