Triple
T22270672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre Dame–USC football rivalry |
E550465
|
entity |
| Predicate | trophyDecoration |
P38093
|
FINISHED |
| Object | jeweled emblems representing game results |
—
|
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: jeweled emblems representing game results | Statement: [Notre Dame–USC football rivalry, trophyDecoration, jeweled emblems representing game results]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyDecoration Context triple: [Notre Dame–USC football rivalry, trophyDecoration, jeweled emblems representing game results]
-
A.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
B.
commemorativeTrophy
Indicates that a trophy exists to honor or memorialize a particular person, event, or achievement.
-
C.
trophyDesigner
Indicates that one entity is the designer or creator of a particular trophy associated with another entity.
-
D.
trophyUse
Indicates that an entity uses, employs, or utilizes a trophy in some manner or context.
-
E.
trophyFeatures
chosen
Indicates that a trophy possesses or is characterized by certain features or attributes.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bf53a481909e2c79de4144f332 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.