Triple
T23553994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin C |
E578128
|
entity |
| Predicate | coversAreaOutside |
P152774
|
FINISHED |
| Object | Berlin fare zone A |
—
|
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 fare zone A | Statement: [Berlin C, coversAreaOutside, Berlin fare zone A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversAreaOutside Context triple: [Berlin C, coversAreaOutside, Berlin fare zone A]
-
A.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
B.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
C.
liesOutside
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
-
D.
includesAreasOff
Indicates that something encompasses or covers areas that are turned off, inactive, or excluded from normal operation.
-
E.
coveredArea
Indicates that one entity occupies or extends over a specific spatial region or surface area associated with another 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed17fc881908b45dcde14790d42 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:12 p.m.