Triple
T23553996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin C |
E578128
|
entity |
| Predicate | outerRingOf |
P56525
|
FINISHED |
| Object | Berlin public transport network |
—
|
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 public transport network | Statement: [Berlin C, outerRingOf, Berlin public transport network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerRingOf Context triple: [Berlin C, outerRingOf, Berlin public transport network]
-
A.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
-
B.
hasOuterBoundaryRadius
Indicates that an entity has an outer boundary characterized by a specific radius measurement.
-
C.
hasOuterRingComponent
chosen
Indicates that an entity includes another entity as a component specifically located in its outer ring.
-
D.
hasInnerRing
Indicates that one entity possesses or contains an inner ring as a component or structural feature of itself.
-
E.
isOuterRingComparedTo
Indicates that one entity is positioned in an outer ring relative to another entity, which lies in an inner or more central ring.
- 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_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. |
Created at: April 17, 2026, 6:12 p.m.