Triple
T11293297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macca’s |
E267383
|
entity |
| Predicate | associatedWithMenuItem |
P70956
|
FINISHED |
| Object | hamburgers |
—
|
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: hamburgers | Statement: [Macca’s, associatedWithMenuItem, hamburgers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMenuItem Context triple: [Macca’s, associatedWithMenuItem, hamburgers]
-
A.
associatedWithAction
Indicates a general relationship where an entity is linked or connected to a particular action, without specifying the nature or direction of that involvement.
-
B.
associatedItem
chosen
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
C.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
D.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
E.
associatedWithMode
Indicates a relationship in which something is linked or connected to a particular mode, method, or manner of operation or behavior.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98b149481909f432a6b9ef8bfbb |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.