Triple
T28880715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | belongsToObservingRun |
P193051
|
FINISHED |
| Object | LIGO-Virgo O2 |
—
|
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 O2 | Statement: [GW170814, belongsToObservingRun, LIGO-Virgo O2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToObservingRun Context triple: [GW170814, belongsToObservingRun, LIGO-Virgo O2]
-
A.
isObservedIn
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
B.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
-
C.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
D.
isObservedFrom
Indicates that one entity serves as the vantage point or location from which another entity is perceived, measured, or monitored.
-
E.
hasObservationRole
Indicates that an entity participates in an observation specifically in the capacity of a defined role (such as observer, subject, or instrument).
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: April 28, 2026, 7:43 a.m.