Triple
T36082588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin S-Bahn fare zone A |
E1043689
|
entity |
| Predicate | isInnermostZoneOf |
P61080
|
FINISHED |
| Object | Berlin ABC fare structure |
—
|
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: Berlin ABC fare structure | Statement: [Berlin S-Bahn fare zone A, isInnermostZoneOf, Berlin ABC fare structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInnermostZoneOf Context triple: [Berlin S-Bahn fare zone A, isInnermostZoneOf, Berlin ABC fare structure]
-
A.
outermostZone
Indicates that one entity is the outermost or furthest boundary zone enclosing or surrounding another entity or area.
-
B.
isPrimarilyZonedFor
Indicates that a particular area or property is designated mainly for a specific type of land use under zoning regulations.
-
C.
isSmallestRegionOf
chosen
Indicates that a region is the smallest subregion that still fully corresponds to or represents a given larger entity or area.
-
D.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.