Triple
T25580394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder |
E641224
|
entity |
| Predicate | propagatesAs |
P77529
|
FINISHED |
| Object | longitudinal wave |
—
|
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: longitudinal wave | Statement: [Thunder, propagatesAs, longitudinal wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propagatesAs Context triple: [Thunder, propagatesAs, longitudinal wave]
-
A.
propagates
Indicates that something causes itself, its effects, or its characteristics to spread or be transmitted from one entity, location, or state to others.
-
B.
spreadsAs
Indicates that one entity propagates, extends, or disseminates from another entity or source.
-
C.
propagatorType
Indicates the specific method or model used to propagate or advance a state (such as position, condition, or effect) from one point in time or space to another.
-
D.
propagateAlong
chosen
Indicates that something (such as an effect, signal, or influence) spreads or is transmitted along a specified path, medium, or connection.
-
E.
propagationMethod
Indicates the means or mechanism by which something spreads, reproduces, or is transmitted from one entity or location to another.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f93364308190bcffdb00ee0ec6c7 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:11 p.m.