Triple
T34167689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wind organ on the boulevard |
E876455
|
entity |
| Predicate | materialSourceOfSound |
P53073
|
FINISHED |
| Object | airflow |
—
|
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: airflow | Statement: [Wind organ on the boulevard, materialSourceOfSound, airflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialSourceOfSound Context triple: [Wind organ on the boulevard, materialSourceOfSound, airflow]
-
A.
materialSource
chosen
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
B.
usesSoundMaterial
Indicates that an entity employs or incorporates sound-based materials (such as audio, recordings, or sonic elements) in its activity, process, or composition.
-
C.
hasSoundboardMaterial
Indicates that one entity has a soundboard made of, or composed from, the material specified by another entity.
-
D.
isSoundProducedBy
Indicates that a particular sound is generated or emitted by a specified source or entity.
-
E.
hasCauseOfSound
Indicates that one entity is the source or origin of a particular sound produced or associated with another entity.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:54 a.m.