Triple
T7891875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Light |
E183253
|
entity |
| Predicate | isFiltered |
P62050
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bud Light, isFiltered, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFiltered Context triple: [Bud Light, isFiltered, yes]
-
A.
hasFilterType
Indicates that an entity is associated with, or constrained by, a specific type or category of filter applied to it.
-
B.
hasFiltration
chosen
Indicates that one entity is equipped with, performs, or is associated with a filtration process or system applied to another entity or substance.
-
C.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
D.
hasRefinement
Indicates that one entity represents a more detailed, specific, or improved version of another entity.
-
E.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39fef2e48190a6282c217c33c57a |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5 p.m.