Triple
T202969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Four |
E4545
|
entity |
| Predicate | selectionMethodForTeams |
P126
|
FINISHED |
| Object | winners of four regional tournaments |
—
|
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: winners of four regional tournaments | Statement: [Final Four, selectionMethodForTeams, winners of four regional tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionMethodForTeams Context triple: [Final Four, selectionMethodForTeams, winners of four regional tournaments]
-
A.
selectionMethodChangedBy
Indicates that one entity causes or is responsible for a change in the method or criteria used to make a selection.
-
B.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
C.
typeOfTeams
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
D.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.