Triple
T28943803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O3 |
E730525
|
entity |
| Predicate | usesDetectorNetwork |
P111587
|
FINISHED |
| Object | LIGO–Virgo gravitational-wave detector network |
—
|
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: LIGO–Virgo gravitational-wave detector network | Statement: [O3, usesDetectorNetwork, LIGO–Virgo gravitational-wave detector network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDetectorNetwork Context triple: [O3, usesDetectorNetwork, LIGO–Virgo gravitational-wave detector network]
-
A.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
-
B.
isDetector
Indicates that one entity functions as a detector for, or is responsible for detecting, another entity or phenomenon.
-
C.
usedInDetector
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
-
D.
usedByNetwork
chosen
Indicates that something is utilized or operated by a particular network.
-
E.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 8:38 a.m.