Triple
T11820781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milk Cup |
E281120
|
entity |
| Predicate | usedAsOfficialNameIn |
P5304
|
FINISHED |
| Object | media coverage |
—
|
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: media coverage | Statement: [Milk Cup, usedAsOfficialNameIn, media coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsOfficialNameIn Context triple: [Milk Cup, usedAsOfficialNameIn, media coverage]
-
A.
usedInOfficialDocumentsOf
chosen
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or jurisdiction.
-
B.
formerOfficialNameOf
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
C.
officiallyAdopted
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
-
D.
notOfficialNameOf
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
E.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e87e488190905bc3bb6d721e56 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.