Triple
T1327961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 7 |
E28372
|
entity |
| Predicate | oftenRememberedFor |
P22
|
FINISHED |
| Object | iconic plays |
—
|
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: iconic plays | Statement: [Game 7, oftenRememberedFor, iconic plays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRememberedFor Context triple: [Game 7, oftenRememberedFor, iconic plays]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
C.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
D.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
E.
commemoratedPerson
Indicates that the subject serves as a memorial or tribute to the referenced person.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.