Triple
T6363272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Club |
E143162
|
entity |
| Predicate | hasCustomerSupport |
P41839
|
FINISHED |
| Object | Royal Jordanian customer service |
—
|
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: Royal Jordanian customer service | Statement: [Royal Club, hasCustomerSupport, Royal Jordanian customer service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerSupport Context triple: [Royal Club, hasCustomerSupport, Royal Jordanian customer service]
-
A.
hasSupportService
chosen
Indicates that one entity provides or is associated with a support-related service for another entity.
-
B.
hasCustomerServiceChannel
Indicates that an entity provides or is associated with a specific channel or medium through which customer service interactions can occur.
-
C.
hasAgencySupport
Indicates that an entity receives backing, assistance, or sponsorship from an agency.
-
D.
hasCustomerAssistanceArea
Indicates that an entity includes or provides a designated area or facility for assisting customers.
-
E.
hasCustomerServiceOperationsIn
Indicates that an entity conducts customer service activities or maintains customer support functions within a specified location or region.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680d51a4819098a6bcd3dfd73be4 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.