Triple
T19601559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference First Round |
E470488
|
entity |
| Predicate | typicalMatchup |
P27263
|
FINISHED |
| Object | 1st seed vs 8th seed |
—
|
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: 1st seed vs 8th seed | Statement: [Eastern Conference First Round, typicalMatchup, 1st seed vs 8th seed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchup Context triple: [Eastern Conference First Round, typicalMatchup, 1st seed vs 8th seed]
-
A.
typicalMatchDay
Indicates that the relationship or conditions described correspond to what normally happens on a standard or usual match day.
-
B.
matchupFrequency
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
definingMatchup
Indicates a matchup that is especially significant or decisive in defining the outcome, narrative, or importance of a broader event or competition.
-
E.
typicalMatchType
chosen
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407f1fd88190aa82c4c96f755584 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.