Triple
T28861998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MANOVA |
E728887
|
entity |
| Predicate | canTest |
P5435
|
FINISHED |
| Object | main effects of factors on multiple outcomes |
—
|
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: main effects of factors on multiple outcomes | Statement: [MANOVA, canTest, main effects of factors on multiple outcomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTest Context triple: [MANOVA, canTest, main effects of factors on multiple outcomes]
-
A.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
B.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
C.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
D.
theoryTested
Indicates that a theory has been subjected to evaluation or experimentation to assess its validity or accuracy.
-
E.
testType
chosen
Indicates the specific category or kind of test associated with an entity or event.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a1821048190a425206bbc20deda |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:47 a.m.