Triple
T32713240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 NBA Finals |
E836452
|
entity |
| Predicate | championTeamCity |
P15127
|
FINISHED |
| Object | Philadelphia |
—
|
NE NERFINISHED |
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: Philadelphia | Statement: [1967 NBA Finals, championTeamCity, Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championTeamCity Context triple: [1967 NBA Finals, championTeamCity, Philadelphia]
-
A.
cityOfChampion
chosen
Indicates that a particular city is recognized as the home or representative city of a given champion or championship-winning entity.
-
B.
championTeamFullName
Indicates the full official name of the team that won a championship or competition.
-
C.
homeTeamChampion
Indicates that the team playing at home is the champion or title-holding team in the given context.
-
D.
hostTeamCity
Indicates the city where the host team is based or where it plays its home events.
-
E.
championQualifiedTeam
Indicates that a team has successfully qualified to participate in a championship 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:11 a.m.