Triple
T8912571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-test |
E212218
|
entity |
| Predicate | hasNullHypothesis |
P86344
|
FINISHED |
| Object | variances are equal |
—
|
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: variances are equal | Statement: [F-test, hasNullHypothesis, variances are equal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNullHypothesis Context triple: [F-test, hasNullHypothesis, variances are equal]
-
A.
hasAlternativeHypothesisLocation
Indicates that there is another possible location proposed as an alternative to the primary hypothesized location.
-
B.
proposesHypothesis
Indicates that one entity puts forward a tentative explanation or hypothesis for consideration regarding another entity or phenomenon.
-
C.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
D.
declineHypothesis
Indicates that a previously proposed hypothesis is being rejected or considered no longer valid.
-
E.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6525d1408190a76522d7c4ac37da |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc604965c48190bbb6db0ae8108e67 |
completed | April 1, 2026, 12:01 a.m. |
Created at: March 30, 2026, 6:56 p.m.