Triple
T2091529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trouton–Noble experiment |
E32680
|
entity |
| Predicate | predictionFrom |
P23826
|
FINISHED |
| Object | aether theory |
—
|
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: aether theory | Statement: [Trouton–Noble experiment, predictionFrom, aether theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictionFrom Context triple: [Trouton–Noble experiment, predictionFrom, aether theory]
-
A.
predictedIn
chosen
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
confirmedPredictionOf
Indicates that a previously made prediction about an entity or event has been verified as accurate or true.
-
C.
predicate
Indicates that a specified relationship or action holds between given entities, without specifying its particular nature.
-
D.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
E.
predicateOf
Indicates that one entity functions as a predicate or predicative expression that attributes a property, relation, or condition to 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_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.