Triple
T11020705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statesman |
E260479
|
entity |
| Predicate | usesCoverNameTheme |
P24958
|
FINISHED |
| Object | alcoholic beverages |
—
|
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: alcoholic beverages | Statement: [Statesman, usesCoverNameTheme, alcoholic beverages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoverNameTheme Context triple: [Statesman, usesCoverNameTheme, alcoholic beverages]
-
A.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
B.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
C.
hasCoverArtTheme
chosen
Indicates that an item’s cover art visually represents or is characterized by a particular theme or motif.
-
D.
usesCodenameTheme
Indicates that an entity adopts a consistent codename pattern or motif (e.g., colors, planets, mythological figures) for naming related items or agents.
-
E.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797baad408190a53fd6941a750f68 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.