Triple
T16053027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Transit Zone |
E389401
|
entity |
| Predicate | fareBoundaryType |
P105131
|
FINISHED |
| Object | zonal 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: zonal boundary | Statement: [City Transit Zone, fareBoundaryType, zonal boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareBoundaryType Context triple: [City Transit Zone, fareBoundaryType, zonal boundary]
-
A.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
B.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
C.
boundaryName
Indicates the designated name or label assigned to a specific boundary or border between entities.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
hasFareBoundary
chosen
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.