Triple
T28943535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW150914 |
E730519
|
entity |
| Predicate | detectedAt |
P53467
|
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: [GW150914, detectedAt, LIGO Hanford Observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectedAt Context triple: [GW150914, detectedAt, LIGO Hanford Observatory]
-
A.
firstDetectedOn
Indicates the date or time when something was initially observed, discovered, or recorded for the first time.
-
B.
detected
chosen
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
C.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
D.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
E.
investigatedAt
Indicates that an investigation into an entity or event took place at a specific location or facility.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 8:38 a.m.