Triple
T17145003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Bell March |
E416065
|
entity |
| Predicate | hasOnlineAudio |
P126286
|
FINISHED |
| Object | available on public-domain recording archives |
—
|
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: available on public-domain recording archives | Statement: [Liberty Bell March, hasOnlineAudio, available on public-domain recording archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineAudio Context triple: [Liberty Bell March, hasOnlineAudio, available on public-domain recording archives]
-
A.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
D.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
E.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2da515481909d19e421382eb755 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.