Triple
T32773211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobra Beer |
E838119
|
entity |
| Predicate | designedToPairWith |
P9494
|
FINISHED |
| Object | spicy food |
—
|
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: spicy food | Statement: [Cobra Beer, designedToPairWith, spicy food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToPairWith Context triple: [Cobra Beer, designedToPairWith, spicy food]
-
A.
canBondWith
Indicates that one entity has the capability or compatibility to form a bond or connection with another entity.
-
B.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
C.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
D.
intendedDockingPartner
Indicates that one entity is designated or expected to connect, interface, or dock with a specific counterpart as its planned partner.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 1, 2026, 1:13 a.m.