Triple
T27546340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TBT Enterprises |
E695371
|
entity |
| Predicate | roleInTheBasketballTournament |
P125127
|
FINISHED |
| Object | event organizer |
—
|
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: event organizer | Statement: [TBT Enterprises, roleInTheBasketballTournament, event organizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheBasketballTournament Context triple: [TBT Enterprises, roleInTheBasketballTournament, event organizer]
-
A.
roleInBasketball
chosen
Indicates the specific function or position an entity holds within the context of playing or organizing a game of basketball.
-
B.
roleAtStadium
Indicates that an entity holds a specific role, function, or position associated with a particular stadium.
-
C.
roleAtMatches
Indicates that an entity’s role or position at a given time or context matches a specified role criterion.
-
D.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
-
E.
roleInWorldCup
Indicates the specific capacity or function an entity had in the context of a World Cup tournament (e.g., player, coach, referee, host).
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 27, 2026, 1:33 p.m.