Triple
T25809771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restaurant Brands International |
E650073
|
entity |
| Predicate | coreProductType |
P90900
|
FINISHED |
| Object | burgers |
—
|
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: burgers | Statement: [Restaurant Brands International, coreProductType, burgers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreProductType Context triple: [Restaurant Brands International, coreProductType, burgers]
-
A.
typeOfProducts
chosen
Indicates the kinds or categories of products that are associated with or offered by an entity.
-
B.
productTypeEvaluated
Indicates that an entity’s product type has been assessed or judged according to certain criteria or standards.
-
C.
developedProductType
Indicates that an entity (such as a project, activity, or organization) has resulted in or produced a specific type of product.
-
D.
productRole
Indicates the functional role or purpose that a product has within a broader system, context, or usage scenario.
-
E.
inUniverseProductType
Indicates that a product belongs to or is categorized within a specific fictional or defined universe or setting.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c37d40819086cc056057c25629 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:08 a.m.