Triple
T32282634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passive Seismic Experiment |
E824741
|
entity |
| Predicate | detectedPhenomenon |
P143678
|
FINISHED |
| Object | shallow moonquakes |
—
|
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: shallow moonquakes | Statement: [Passive Seismic Experiment, detectedPhenomenon, shallow moonquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectedPhenomenon Context triple: [Passive Seismic Experiment, detectedPhenomenon, shallow moonquakes]
-
A.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
B.
encounteredPhenomenon
chosen
Indicates that an entity has come across, experienced, or observed a particular phenomenon.
-
C.
examplePhenomenon
Indicates a representative or illustrative occurrence used to demonstrate or clarify a broader phenomenon or pattern.
-
D.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
E.
demonstratedPhenomenon
Indicates that an entity has shown, exhibited, or provided evidence for the occurrence of a particular phenomenon.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bccc5be081908b121f4035b42dd9 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.