Triple
T2091523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trouton–Noble experiment |
E32680
|
entity |
| Predicate | testedHypothesis |
P17991
|
FINISHED |
| Object | existence of luminiferous aether |
—
|
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: existence of luminiferous aether | Statement: [Trouton–Noble experiment, testedHypothesis, existence of luminiferous aether]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedHypothesis Context triple: [Trouton–Noble experiment, testedHypothesis, existence of luminiferous aether]
-
A.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
B.
appliedTest
chosen
Indicates that a test has been administered or carried out on a particular subject or object.
-
C.
declineHypothesis
Indicates that a previously proposed hypothesis is being rejected or considered no longer valid.
-
D.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
E.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba7626d081908c9c0f18942e128d |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.