Triple
T28880692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasDetectorSite |
P6781
|
FINISHED |
| Object | LIGO Hanford Observatory |
—
|
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 Hanford Observatory | Statement: [GW170814, hasDetectorSite, LIGO Hanford Observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectorSite Context triple: [GW170814, hasDetectorSite, LIGO Hanford Observatory]
-
A.
hasFindingSite
Indicates that a particular finding, observation, or abnormality is located in or associated with a specific anatomical site.
-
B.
hasModeOfDetection
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
C.
isDetector
Indicates that one entity functions as a detector for, or is responsible for detecting, another entity or phenomenon.
-
D.
hasObservationSite
chosen
Indicates that something (such as a measurement, event, or observation activity) is associated with or took place at a specific observation site or location.
-
E.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 28, 2026, 7:43 a.m.