Triple
T14257323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin ABC fare zones |
E353417
|
entity |
| Predicate | hasZoneStructure |
P113467
|
FINISHED |
| Object | concentric |
—
|
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: concentric | Statement: [Berlin ABC fare zones, hasZoneStructure, concentric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoneStructure Context triple: [Berlin ABC fare zones, hasZoneStructure, concentric]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasZoneStatus
Indicates that a specified zone currently possesses a particular status or condition.
-
C.
supportsZoneSystem
Indicates that one entity provides compatibility with or implementation of a specific zone-based system used by another entity.
-
D.
hasZoningPolicy
Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
-
E.
numberOfZones
Indicates the quantity of distinct zones associated with or contained by a given entity.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6352611c819090d062fe3079cd03 |
completed | April 14, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:09 a.m.