Triple
T25809883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Double coffee |
E650076
|
entity |
| Predicate | hasOrderingPhrase |
P167059
|
FINISHED |
| Object | double double |
—
|
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: double double | Statement: [Double Double coffee, hasOrderingPhrase, double double]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderingPhrase Context triple: [Double Double coffee, hasOrderingPhrase, double double]
-
A.
hasOrderingMethod
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
hasBasicWordOrder
Indicates the typical sequence in which core sentence elements (such as subject, verb, and object) are ordered in a language.
-
D.
hasNameOrder
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
E.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- F. None of above. chosen
Provenance (4 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 22, 2026, 7:08 a.m.