Triple
T200013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA champion |
E4082
|
entity |
| Predicate | fanTraditions |
P6226
|
FINISHED |
| Object | championship parade |
—
|
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: championship parade | Statement: [NBA champion, fanTraditions, championship parade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanTraditions Context triple: [NBA champion, fanTraditions, championship parade]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
-
C.
fanbaseCharacteristic
chosen
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
D.
hallOfFameAssociation
Indicates that an entity is formally associated with a hall of fame, such as through induction, nomination, or recognition.
-
E.
playsForFranchise
Indicates that one entity is an athlete or performer who is a member of, or competes on behalf of, a particular sports franchise or team.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcc6dc88190b8c24b485588dfe4 |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.