Triple
T8912677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisher's exact test |
E212220
|
entity |
| Predicate | preferredWhen |
P37215
|
FINISHED |
| Object | sample size is small |
—
|
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: sample size is small | Statement: [Fisher's exact test, preferredWhen, sample size is small]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredWhen Context triple: [Fisher's exact test, preferredWhen, sample size is small]
-
A.
isPreferredWhen
chosen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
-
B.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
C.
favored
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
D.
priorityBenefit
Indicates that one benefit takes precedence over or is considered more important than another in a given context.
-
E.
preferredLight
Indicates that one entity favors or is best suited to a particular lighting condition or level of illumination.
- 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_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. |
Created at: March 30, 2026, 6:56 p.m.