Triple
T8396756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIGO Scientific Collaboration |
E198071
|
entity |
| Predicate | madeDiscoveryOn |
P82006
|
FINISHED |
| Object | 2015-09-14 |
—
|
LITERAL FINISHED |
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: 2015-09-14 | Statement: [LIGO Scientific Collaboration, madeDiscoveryOn, 2015-09-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeDiscoveryOn Context triple: [LIGO Scientific Collaboration, madeDiscoveryOn, 2015-09-14]
-
A.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
B.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
C.
discoveredFeature
Indicates that an entity has identified or uncovered a previously unknown or unrecognized feature of another entity or object.
-
D.
reportsDiscoveryOf
Indicates that one entity formally announces or documents the finding or uncovering of another entity (typically a new object, fact, or phenomenon).
-
E.
discoveredArtifact
Indicates that an entity has found or uncovered a previously unknown or hidden artifact.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb818893348190a6ea2ff6a2e3e491 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:04 p.m.