Triple
T58075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Finals games |
E1149
|
entity |
| Predicate | homeCourtAdvantageCriteria |
P136
|
FINISHED |
| Object | better regular-season record |
—
|
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: better regular-season record | Statement: [NBA Finals games, homeCourtAdvantageCriteria, better regular-season record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCourtAdvantageCriteria Context triple: [NBA Finals games, homeCourtAdvantageCriteria, better regular-season record]
-
A.
hasAdvantage
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
-
B.
homeFieldOpened
Indicates that a team's designated home field has officially begun operation or been opened for use.
-
C.
eligibilityCriteria
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
D.
awardCriteria
Indicates the standards or conditions used to determine eligibility for receiving an award or recognition.
-
E.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24c9057348190aa6692eeeae19569 |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac7547c81909bb68f327cdb9158 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.