Triple
T15961380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kruskal–Wallis test |
E387065
|
entity |
| Predicate | parameterSymbol |
P12016
|
FINISHED |
| Object | k |
—
|
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: k | Statement: [Kruskal–Wallis test, parameterSymbol, k]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterSymbol Context triple: [Kruskal–Wallis test, parameterSymbol, k]
-
A.
parameter
chosen
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
C.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
-
D.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
-
E.
parametrizes
Indicates that one entity defines or controls the variable parameters that determine the behavior, form, or configuration of 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_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.