Triple
T5870649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Etrusco Unico |
E130506
|
entity |
| Predicate | circumferenceStandard |
P41831
|
FINISHED |
| Object | FIFA-approved match ball |
—
|
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: FIFA-approved match ball | Statement: [Adidas Etrusco Unico, circumferenceStandard, FIFA-approved match ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circumferenceStandard Context triple: [Adidas Etrusco Unico, circumferenceStandard, FIFA-approved match ball]
-
A.
circumference
Indicates the total length around the boundary of a closed curve, typically a circle, relating a shape to the measure of its perimeter.
-
B.
baseCircumference
Indicates the circumference measurement of the base of an object or geometric figure.
-
C.
standardRoundLength
Indicates that there is a defined, typical duration assigned to a single round within a process, activity, or game.
-
D.
distanceStandard
Indicates that a specified distance between entities is measured or evaluated according to a particular standard or reference criterion.
-
E.
standardWithin
chosen
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.