Triple
T34090671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup ring |
E874294
|
entity |
| Predicate | traditionSimilarTo |
P11721
|
FINISHED |
| Object | Super Bowl ring |
—
|
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: Super Bowl ring | Statement: [MLS Cup ring, traditionSimilarTo, Super Bowl ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionSimilarTo Context triple: [MLS Cup ring, traditionSimilarTo, Super Bowl ring]
-
A.
traditionAssociatesWith
Indicates that a particular tradition is connected or linked to another entity, such as a practice, group, place, or concept.
-
B.
sharesTraditionsWith
chosen
Indicates that two entities have customs, practices, or cultural traditions in common or mutually observe similar traditional activities.
-
C.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 1:52 a.m.