Triple
T1327959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 7 |
E28372
|
entity |
| Predicate | oftenDescribedAs |
P21265
|
FINISHED |
| Object | winner-take-all game |
—
|
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: winner-take-all game | Statement: [Game 7, oftenDescribedAs, winner-take-all game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDescribedAs Context triple: [Game 7, oftenDescribedAs, winner-take-all game]
-
A.
isFrequentlyDescribedAs
chosen
Indicates that something is often characterized or referred to using a particular description or set of attributes.
-
B.
oftenDepictedAs
Indicates that one entity is frequently represented or portrayed in the form, appearance, or symbolism of another entity.
-
C.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
D.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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.