Triple
T14911078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tukey's fences |
E371260
|
entity |
| Predicate | definesLowerExtremeFence |
P39203
|
FINISHED |
| Object | Q1 - 3 × IQR |
—
|
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: Q1 - 3 × IQR | Statement: [Tukey's fences, definesLowerExtremeFence, Q1 - 3 × IQR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesLowerExtremeFence Context triple: [Tukey's fences, definesLowerExtremeFence, Q1 - 3 × IQR]
-
A.
isLowestCrossingOf
Indicates that one crossing among several possible crossings between entities occurs at the lowest position or level in a given ordering or structure.
-
B.
hasLowerBoundaryDefinedBy
chosen
Indicates that one entity’s lower limit, edge, or boundary is specified or determined by another entity.
-
C.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
D.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
E.
knownLowerBoundProvedBy
Indicates that a specific lower bound has been formally established or proven by a particular method, proof, or source.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61c6b9c8190a92934d49b98fe46 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:26 a.m.