Triple
T15409300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkers franchises |
E368541
|
entity |
| Predicate | menuPositioning |
P9544
|
FINISHED |
| Object | value menu items |
—
|
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: value menu items | Statement: [Checkers franchises, menuPositioning, value menu items]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menuPositioning Context triple: [Checkers franchises, menuPositioning, value menu items]
-
A.
ingredientPositioning
Indicates the spatial or ordered arrangement of ingredients relative to one another within a composition or structure.
-
B.
positioning
chosen
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
C.
ribbonPosition
Indicates the spatial or ordered placement of a ribbon relative to a reference object or coordinate system.
-
D.
buttonPlacement
Indicates the spatial or positional arrangement of a button relative to other elements or within a given interface or context.
-
E.
hasPositioning
Indicates that one entity occupies, is arranged in, or is assigned a specific spatial or relative position with respect to another entity or reference frame.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea4f13c819085d26fd32b5dca6f |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.