Triple
T11271298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sioux Crew |
E266818
|
entity |
| Predicate | cheersAt |
P83292
|
FINISHED |
| Object | home games |
—
|
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: home games | Statement: [The Sioux Crew, cheersAt, home games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheersAt Context triple: [The Sioux Crew, cheersAt, home games]
-
A.
cupWonWith
Indicates that a particular cup or tournament victory was achieved using or in association with a specified entity (such as a team, player, or equipment).
-
B.
isCelebratoryOf
chosen
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
-
C.
hasChampagneBar
Indicates that an entity includes, features, or is equipped with a champagne bar.
-
D.
publicCelebration
Indicates a relationship where an event, achievement, or occasion is celebrated openly and collectively in a public setting.
-
E.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9506204819089dc0827483bd948 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.