Triple
T17686223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-12 Conference men's soccer |
E440893
|
entity |
| Predicate | usesCompetitionBall |
P99353
|
FINISHED |
| Object | soccer 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: soccer ball | Statement: [Pac-12 Conference men's soccer, usesCompetitionBall, soccer ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCompetitionBall Context triple: [Pac-12 Conference men's soccer, usesCompetitionBall, soccer ball]
-
A.
usesBallSport
Indicates that an activity or event involves the use of a ball as part of a sport.
-
B.
ballOrObjectUsed
chosen
Indicates that a ball or other object is used as the instrument or tool in performing an action or event.
-
C.
usesBallColor
Indicates that an entity performs an action or operates in a way that depends on or involves the color of a ball.
-
D.
usesBallShape
Indicates that one entity employs or incorporates a ball-like (spherical) shape in its form, design, or operation.
-
E.
playsOnSideOfBall
Indicates that one entity participates in a game or sport on a particular side or unit of the ball (e.g., offense or defense).
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47047d90c8190a172201f3de6db87 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:02 a.m.