Triple
T33867679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-35 rivalry |
E868101
|
entity |
| Predicate | playoffMeetingFrequency |
P10401
|
FINISHED |
| Object | recurring |
—
|
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: recurring | Statement: [I-35 rivalry, playoffMeetingFrequency, recurring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffMeetingFrequency Context triple: [I-35 rivalry, playoffMeetingFrequency, recurring]
-
A.
playoffMeetingsCount
Indicates the number of times the entities have faced each other in playoff competitions.
-
B.
playoffMeetingsEra
Indicates that two entities have faced each other in playoff competition during a specified historical era or time period.
-
C.
playoffMeetingExample
Indicates that two competitors or teams are involved together in a specific playoff matchup or series.
-
D.
hasPlayoffMeetings
chosen
Indicates that the entities have faced each other in playoff competitions or postseason matchups.
-
E.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a3bf1c819099666c5ad645eea2 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.