Triple
T798539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Region |
E17075
|
entity |
| Predicate | tournamentPhase |
P2703
|
FINISHED |
| Object | early rounds |
—
|
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: early rounds | Statement: [East Region, tournamentPhase, early rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentPhase Context triple: [East Region, tournamentPhase, early rounds]
-
A.
competitionStage
chosen
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
B.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
C.
isPreseasonTournamentFor
Indicates that a tournament takes place before the regular season and serves as a preparatory competition for a specific main season or league.
-
D.
hasGroupStage
Indicates that an entity includes, participates in, or is associated with a specific group stage within a larger multi-stage structure or process.
-
E.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b4d9548190aad5fdf1211cf8cd |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.