Triple
T15961377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kruskal–Wallis test |
E387065
|
entity |
| Predicate | testStatistic |
P86343
|
FINISHED |
| Object | H statistic |
—
|
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: H statistic | Statement: [Kruskal–Wallis test, testStatistic, H statistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testStatistic Context triple: [Kruskal–Wallis test, testStatistic, H statistic]
-
A.
hasTestStatistic
chosen
Indicates that a given test or analysis is associated with a specific numerical test statistic value.
-
B.
statisticNote
Indicates that there is an explanatory note or comment providing additional context or clarification about a reported statistic.
-
C.
hasStatistics
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
D.
statisticMeasured
Indicates that a particular statistic or quantitative measure is obtained from, or used to evaluate, a given entity or phenomenon.
-
E.
statValue
Indicates that an entity has a particular statistical attribute with a specified value.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.