Triple
T27131365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Meal |
E681570
|
entity |
| Predicate | typicalSideOption |
P70748
|
FINISHED |
| Object | French fries |
—
|
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: French fries | Statement: [Happy Meal, typicalSideOption, French fries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSideOption Context triple: [Happy Meal, typicalSideOption, French fries]
-
A.
typicalVenueSide
Indicates the usual or standard side or location within a venue where something (such as an activity, feature, or participant) is typically situated or occurs.
-
B.
typicalOption
Indicates that one option is considered standard, common, or most representative among a set of possible options.
-
C.
sideType
Indicates the specific role or position an entity occupies within a two-sided or multi-sided relationship (e.g., buyer vs. seller, left vs. right side).
-
D.
servesSide
Indicates that one entity is provided or presented as an accompanying side item to another primary entity.
-
E.
hasTypicalSide
chosen
Indicates that one entity is the usual or characteristic side (e.g., lateral aspect) associated with another entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 27, 2026, 9:04 a.m.