Triple
T17353134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force lightning |
E421862
|
entity |
| Predicate | soundSignature |
P19774
|
FINISHED |
| Object | crackling electrical discharge |
—
|
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: crackling electrical discharge | Statement: [Force lightning, soundSignature, crackling electrical discharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundSignature Context triple: [Force lightning, soundSignature, crackling electrical discharge]
-
A.
signatureSound
chosen
Indicates that something has a distinctive, characteristic sound that uniquely identifies it.
-
B.
soundMotif
Indicates a recurring or thematically significant sound pattern associated with an entity, event, or context.
-
C.
signatureTuneOf
Indicates that one entity is the characteristic or officially recognized musical theme associated with another entity.
-
D.
signatureFeature
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
E.
soundCharacter
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.