Triple
T22272010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 official ball |
E550500
|
entity |
| Predicate | weightSize |
P147649
|
FINISHED |
| Object | size 7 |
—
|
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 7 | Statement: [FIBA 3x3 official ball, weightSize, size 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightSize Context triple: [FIBA 3x3 official ball, weightSize, size 7]
-
A.
sizeType
Indicates the kind or category of size associated with an entity, such as relative scale, measurement type, or size classification.
-
B.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
C.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
D.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
E.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
- F. None of above. chosen
Provenance (4 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea449648190bb89ca292d32f59d |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.