Triple
T8546643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gongman |
E202343
|
entity |
| Predicate | isSoundAssociated |
P22084
|
FINISHED |
| Object | gong strike |
—
|
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: gong strike | Statement: [Gongman, isSoundAssociated, gong strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSoundAssociated Context triple: [Gongman, isSoundAssociated, gong strike]
-
A.
hasSound
chosen
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
-
C.
includesAddedSound
Indicates that one entity contains or incorporates an additional sound element beyond the original or primary audio content.
-
D.
usesSoundDevice
Indicates that one entity operates or relies on a sound-producing or sound-processing device in relation to another entity or context.
-
E.
followsSoundOf
Indicates that one entity moves or directs its attention by tracking the source or direction of a sound produced by 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe7511f8c819083d69fb6a0b55801 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.