Triple
T8695900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Gift Card |
E206401
|
entity |
| Predicate | hasCustomerServiceNumber |
P64214
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Disney Gift Card, hasCustomerServiceNumber, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerServiceNumber Context triple: [Disney Gift Card, hasCustomerServiceNumber, true]
-
A.
hasCustomerServiceChannel
Indicates that an entity provides or is associated with a specific channel or medium through which customer service interactions can occur.
-
B.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
C.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
D.
hasCallInNumber
chosen
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
E.
serviceNumberLabel
Indicates that a label or identifier is assigned to denote the service number associated with an 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582996a0819097ad03097ad1f103 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.