Triple
T22517496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bintang Beer |
E556685
|
entity |
| Predicate | consumerGroup |
P82393
|
FINISHED |
| Object | locals in Indonesia |
—
|
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: locals in Indonesia | Statement: [Bintang Beer, consumerGroup, locals in Indonesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consumerGroup Context triple: [Bintang Beer, consumerGroup, locals in Indonesia]
-
A.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
B.
customerGroup
chosen
Indicates a relationship in which an entity belongs to, is classified under, or is associated with a particular group of customers.
-
C.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
D.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
E.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2df59c81909c4ae2f20f1cbb32 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.