Triple
T15830193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler Objects of Interest |
E383847
|
entity |
| Predicate | signalSourcesMayInclude |
P40631
|
FINISHED |
| Object | instrumental noise |
—
|
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: instrumental noise | Statement: [Kepler Objects of Interest, signalSourcesMayInclude, instrumental noise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalSourcesMayInclude Context triple: [Kepler Objects of Interest, signalSourcesMayInclude, instrumental noise]
-
A.
samplingSource
Indicates that one entity serves as the origin or provider from which another entity is sampled or drawn.
-
B.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
C.
sourcesInclude
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
-
D.
signalOrigin
chosen
Indicates that one entity is the source or starting point from which a signal is generated or transmitted to others.
-
E.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e636bb48190a6b39feb550aaa3d |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.