Triple
T28880690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | detectedByInstrument |
P62375
|
FINISHED |
| Object | Advanced LIGO |
—
|
NE NERFINISHED |
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: Advanced LIGO | Statement: [GW170814, detectedByInstrument, Advanced LIGO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectedByInstrument Context triple: [GW170814, detectedByInstrument, Advanced LIGO]
-
A.
definedByInstrument
Indicates that something is established, specified, or characterized through the use or application of a particular instrument or tool.
-
B.
isInstrumentFor
Indicates that something is used as a tool or means to perform a particular action or achieve a specific outcome.
-
C.
formedByInstrument
Indicates that something is created, produced, or brought into existence through the use or action of a specific instrument or tool.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
discoveredWithInstrument
chosen
Indicates that something was discovered through the use of a specified instrument or tool.
- 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 7:43 a.m.