Triple
T27131604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quarter Pounder |
E681575
|
entity |
| Predicate | pattyWeightBeforeCooking |
P161876
|
FINISHED |
| Object | approximately 113 grams |
—
|
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: approximately 113 grams | Statement: [Quarter Pounder, pattyWeightBeforeCooking, approximately 113 grams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pattyWeightBeforeCooking Context triple: [Quarter Pounder, pattyWeightBeforeCooking, approximately 113 grams]
-
A.
pattyWeightBeforeCooking
chosen
Indicates the weight of a patty measured prior to the cooking process.
-
B.
typicalCookingTime
Indicates the usual duration required to cook something under standard or commonly accepted conditions.
-
C.
meatPreparation
Indicates the method or process by which meat is treated, cooked, or otherwise prepared for consumption.
-
D.
BakerYield
Indicates the amount or output produced by a baker, typically in terms of quantity or volume of baked goods resulting from a given process or batch.
-
E.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
- 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_69f6247832a48190b820e8c0c22ff5db |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:04 a.m.