Triple
T11512072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Footballs |
E272937
|
entity |
| Predicate | standardSize |
P28652
|
FINISHED |
| Object | Size 5 (adult professional) |
—
|
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: Size 5 (adult professional) | Statement: [Adidas Footballs, standardSize, Size 5 (adult professional)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardSize Context triple: [Adidas Footballs, standardSize, Size 5 (adult professional)]
-
A.
standardSetSize
Indicates that there is a defined or typical number of elements that constitute the standard size for a given set.
-
B.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
C.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
D.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
-
E.
sizeDescription
chosen
Indicates a relationship where one entity provides descriptive information about the size or scale 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db7af688190b68668eb39d382a8 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.