Triple
T25184506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Four |
E630678
|
entity |
| Predicate | advancingTeamsFromPreviousRound |
P6988
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Final Four, advancingTeamsFromPreviousRound, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancingTeamsFromPreviousRound Context triple: [Final Four, advancingTeamsFromPreviousRound, 4]
-
A.
advancesTeamsTo
Indicates that one entity causes or marks the progression of one or more teams to a subsequent stage, level, or round in a process or competition.
-
B.
advancesNumberOfTeams
chosen
Indicates that one entity causes an increase in how many teams progress or move forward in a given context.
-
C.
nextRound
Indicates that one event, state, or step directly follows another in the subsequent round or iteration.
-
D.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
E.
championAdvancedTo
Indicates that a champion has progressed from one stage, round, or level of a competition to a more advanced stage.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc9e8fc8190844984493b19b9b1 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:37 p.m.