Triple
T29080973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 3 (Île-de-France fare zone) |
E733980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative transport zone |
C42172
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: administrative transport zone Context triple: [Zone 3 (Île-de-France fare zone), instanceOf, administrative transport zone]
-
A.
transfer zone
A transfer zone is a structural region in the Earth's crust where deformation, stress, or displacement is transferred between adjacent tectonic or sedimentary domains, often linking segments of faults, basins, or plate boundaries.
-
B.
transition zone
A transition zone is a boundary region where two distinct systems, phases, or environments meet and gradually change into one another, exhibiting mixed or intermediate characteristics.
-
C.
demilitarized zone arrangement
A demilitarized zone arrangement is a structured agreement or configuration that establishes a buffer area where military forces, weapons, or hostile activities are restricted or prohibited to reduce conflict and enhance security between opposing parties.
-
D.
Verwaltungseinheit
Eine Verwaltungseinheit ist eine organisatorische Einheit innerhalb einer öffentlichen oder privaten Institution, die für die Erfüllung bestimmter Verwaltungsaufgaben und die Umsetzung von Richtlinien in einem abgegrenzten Zuständigkeitsbereich verantwortlich ist.
-
E.
transit service area
chosen
A transit service area is the geographic region within which a public transportation provider offers routes, stops, and related services to riders.
- F. None of above.
Provenance (1 batch)
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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 10:55 a.m.