Triple
T28943562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW150914 |
E730519
|
entity |
| Predicate | observatoryNetwork |
P106478
|
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: [GW150914, observatoryNetwork, Advanced LIGO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observatoryNetwork Context triple: [GW150914, observatoryNetwork, Advanced LIGO]
-
A.
associatedObservatoryNetwork
chosen
Indicates a relationship where an observatory is linked to, or is a member of, a particular observatory network or system.
-
B.
observatoryOrganization
Indicates that an organization operates, manages, or is institutionally responsible for an observatory.
-
C.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
-
D.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
E.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
- 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_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 8:38 a.m.