Triple
T28124990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Light Lime |
E710901
|
entity |
| Predicate | isAvailableInRegion |
P164567
|
FINISHED |
| Object | North America |
—
|
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: North America | Statement: [Bud Light Lime, isAvailableInRegion, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAvailableInRegion Context triple: [Bud Light Lime, isAvailableInRegion, North America]
-
A.
availableInCountry
Indicates that something can be legally or practically obtained, accessed, or used within a specified country.
-
B.
isPlayedInRegion
Indicates that an instance of something (such as a game, media, or event) is available to be played or occurs within a specified geographic region.
-
C.
ITURegion
Indicates the International Telecommunication Union (ITU) regional classification to which an entity (such as a location or station) belongs.
-
D.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
E.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 9:19 p.m.