Triple
T28880687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasDetectionMethod |
P156114
|
FINISHED |
| Object | gravitational-wave interferometry |
—
|
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: gravitational-wave interferometry | Statement: [GW170814, hasDetectionMethod, gravitational-wave interferometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectionMethod Context triple: [GW170814, hasDetectionMethod, gravitational-wave interferometry]
-
A.
hasModeOfDetection
chosen
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
B.
errorDetectionMethod
Indicates the method or technique used to detect errors in a process, system, or data.
-
C.
hasObservationMethod
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
-
D.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
E.
usesScanningMethod
Indicates that an entity performs or carries out an action by employing a specific scanning method.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 7:43 a.m.