Triple
T202982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Four |
E4545
|
entity |
| Predicate | hostSelectionFrequency |
P85
|
FINISHED |
| Object | several years in advance |
—
|
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: several years in advance | Statement: [Final Four, hostSelectionFrequency, several years in advance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSelectionFrequency Context triple: [Final Four, hostSelectionFrequency, several years in advance]
-
A.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
B.
selectionRankingFrequency
Indicates how often an entity is chosen or ranked in a particular position within a selection or ordering process.
-
C.
hostState
Indicates a relationship where one entity serves as the host or governing state for another entity, within whose jurisdiction, territory, or authority that other entity operates or resides.
-
D.
frequentlyVisitedBy
Indicates that an entity is regularly or often visited by another entity.
-
E.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
- 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.