Triple
T22289687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Questra |
E550958
|
entity |
| Predicate | pressureStandard |
P81648
|
FINISHED |
| Object | conforms to FIFA match ball pressure regulations |
—
|
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: conforms to FIFA match ball pressure regulations | Statement: [Adidas Questra, pressureStandard, conforms to FIFA match ball pressure regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureStandard Context triple: [Adidas Questra, pressureStandard, conforms to FIFA match ball pressure regulations]
-
A.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
B.
typicalPressure
Indicates the usual or characteristic level of pressure typically associated with an entity, situation, or condition.
-
C.
pressureCapability
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
D.
pressureContext
Indicates a situational or environmental condition in which entities experience or exert pressure, stress, or constraint on one another or on a shared context.
-
E.
operatingPressureStandard
chosen
Indicates the standard or specified pressure level at which an operation, system, or component is intended to function.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560adde88190961d8fc24c1c4b3c |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.