Triple
T36524800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statesman whiskey |
E900271
|
entity |
| Predicate | hasBrandUniverse |
P189487
|
FINISHED |
| Object | Kingsman |
—
|
NE NERFINISHED |
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: Kingsman | Statement: [Statesman whiskey, hasBrandUniverse, Kingsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandUniverse Context triple: [Statesman whiskey, hasBrandUniverse, Kingsman]
-
A.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
B.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
hasFictionalUniverseType
Indicates that an entity is associated with, or belongs to, a particular type or category of fictional universe.
-
D.
hasBrandConcept
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
-
E.
hasEntertainmentBrand
Indicates that one entity owns, operates, or is formally associated with an entertainment-related brand or franchise.
- F. None of above. chosen
Provenance (4 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:11 p.m.