Triple
T32713242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 NBA Finals |
E836452
|
entity |
| Predicate | championTeamFranchise |
P61319
|
FINISHED |
| Object | Philadelphia 76ers franchise |
—
|
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 76ers franchise | Statement: [1967 NBA Finals, championTeamFranchise, Philadelphia 76ers franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championTeamFranchise Context triple: [1967 NBA Finals, championTeamFranchise, Philadelphia 76ers franchise]
-
A.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive context.
-
B.
teamFranchise
Indicates that a sports team is associated with, or belongs to, a particular franchise organization.
-
C.
winningTeamFranchise
chosen
Indicates the franchise to which the team that won a given game, event, or competition belongs.
-
D.
team2Franchise
Indicates a relationship where a second team is associated with, or belongs to, a particular franchise.
-
E.
hostTeamFranchise
Indicates that a team franchise is serving as the host team in a given game or event.
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:11 a.m.