Triple
T14162535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Town/Chinatown MAX Station |
E350983
|
entity |
| Predicate | hasZoneStatus |
P113069
|
FINISHED |
| Object | TriMet fare zone (post–Fareless Square era) |
—
|
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: TriMet fare zone (post–Fareless Square era) | Statement: [Old Town/Chinatown MAX Station, hasZoneStatus, TriMet fare zone (post–Fareless Square era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoneStatus Context triple: [Old Town/Chinatown MAX Station, hasZoneStatus, TriMet fare zone (post–Fareless Square era)]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
supportsZoneSystem
Indicates that one entity provides compatibility with or implementation of a specific zone-based system used by another entity.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
hasFreeZone
Indicates that an entity includes or is associated with a designated free zone area where special rules, privileges, or exemptions apply.
-
E.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de613a4a2081908fd51bf4b4d82b6c |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:59 a.m.