Triple
T28943554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW150914 |
E730519
|
entity |
| Predicate | waveformModel |
P166049
|
FINISHED |
| Object | general relativity binary black hole coalescence |
—
|
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: general relativity binary black hole coalescence | Statement: [GW150914, waveformModel, general relativity binary black hole coalescence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveformModel Context triple: [GW150914, waveformModel, general relativity binary black hole coalescence]
-
A.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
B.
waveSource
Indicates that an entity serves as the origin or emitter of a wave affecting another entity or region.
-
C.
wavesSymbolize
Indicates that waves are used as symbols representing particular ideas, emotions, or concepts.
-
D.
waveSelection
Indicates a relationship where a specific wave or waveform is chosen or designated from among multiple possible options.
-
E.
waveLength
Indicates the distance between successive corresponding points (such as peaks) of a wave associated with the related entities.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 8:38 a.m.