Triple
T38601423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleflora |
E934224
|
entity |
| Predicate | orderMethod |
P66539
|
FINISHED |
| Object | credit card payment |
—
|
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: credit card payment | Statement: [Teleflora, orderMethod, credit card payment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderMethod Context triple: [Teleflora, orderMethod, credit card payment]
-
A.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
B.
purchaseMethod
chosen
Indicates the way or channel through which a purchase is made (e.g., online, in-store, by phone, or via a specific payment or ordering method).
-
C.
orderingType
Indicates the specific method or arrangement by which items, events, or entities are ordered or sequenced relative to one another.
-
D.
orderHandling
Indicates how an order is processed, managed, or fulfilled from initiation through completion.
-
E.
orderParameter
Indicates the degree of structural or phase organization in a system, typically quantifying how ordered or coherent its state is relative to disorder.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.