Triple
T34224130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Morgan |
E878000
|
entity |
| Predicate | advertisingCharacter |
P42647
|
FINISHED |
| Object | Captain Morgan mascot |
—
|
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: Captain Morgan mascot | Statement: [Captain Morgan, advertisingCharacter, Captain Morgan mascot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisingCharacter Context triple: [Captain Morgan, advertisingCharacter, Captain Morgan mascot]
-
A.
brandCharacter
chosen
Indicates that one entity serves as a brand character or mascot representing another entity (typically a brand or product).
-
B.
commercialCharacter
Indicates that an entity is a fictional or stylized persona used in a commercial or advertising context.
-
C.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
-
D.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
E.
posterCharacterizes
Indicates that a poster visually or textually portrays and defines the qualities, traits, or identity of something or someone.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.