Triple
T38549771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 NCAA Men’s Final Four |
E925073
|
entity |
| Predicate | hostCityFinalFourCount |
P190895
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [2022 NCAA Men’s Final Four, hostCityFinalFourCount, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityFinalFourCount Context triple: [2022 NCAA Men’s Final Four, hostCityFinalFourCount, 6]
-
A.
FinalFourAppearances
Indicates the number of times a team has reached the semifinal round (Final Four) of a tournament or championship.
-
B.
NCAAFinalFourAppearances
Indicates the number of times a team has reached the semifinal round (Final Four) of the NCAA football championship structure, if such a format is being referenced.
-
C.
finalFourCity
Indicates the city where the Final Four round of a tournament (typically a basketball championship) is held.
-
D.
finalFourHostMetroArea
Indicates the metropolitan area that served as the host location for the Final Four event.
-
E.
NCAAFinalFourAppearance
Indicates that a college football team has reached the semifinal round (final four teams) of the NCAA postseason championship.
- F. None of above. chosen
Provenance (4 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd2e2f00081908b8c820fc073a63c |
completed | May 7, 2026, 5:58 p.m. |
Created at: May 3, 2026, 4:32 p.m.