Triple
T19592794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carillon Berlin |
E470276
|
entity |
| Predicate | hasAcousticRange |
P117332
|
FINISHED |
| Object | outdoor urban area |
—
|
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: outdoor urban area | Statement: [Carillon Berlin, hasAcousticRange, outdoor urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcousticRange Context triple: [Carillon Berlin, hasAcousticRange, outdoor urban area]
-
A.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
B.
isAcoustic
Indicates that something produces sound using natural resonance or mechanical vibration rather than electronic amplification or synthesis.
-
C.
hasAcousticsSuitableFor
chosen
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
D.
hasRadioOutputPowerRange
Indicates the range of possible radio output power levels that an entity can transmit.
-
E.
soundHeardDistanceApproximate
Indicates that a sound was heard at an estimated, not precisely measured, distance from the listener or reference point.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64057460c8190962e2e58f06b3985 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.