Triple
T5887187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Celtics–Philadelphia 76ers rivalry |
E130892
|
entity |
| Predicate | playoffMeetingsCountApprox |
P47166
|
FINISHED |
| Object | over 20 |
—
|
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: over 20 | Statement: [Boston Celtics–Philadelphia 76ers rivalry, playoffMeetingsCountApprox, over 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffMeetingsCountApprox Context triple: [Boston Celtics–Philadelphia 76ers rivalry, playoffMeetingsCountApprox, over 20]
-
A.
playoffMeetingsCount
chosen
Indicates the number of times the entities have faced each other in playoff competitions.
-
B.
hasPlayoffMeetings
Indicates that the entities have faced each other in playoff competitions or postseason matchups.
-
C.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
-
D.
numberOfPlayoffTeams
Indicates the total count of teams that qualify for or participate in the playoffs within a given league or season.
-
E.
playoffMeetingExample
Indicates that two competitors or teams are involved together in a specific playoff matchup or series.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.