Triple
T32563161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Miles |
E832280
|
entity |
| Predicate | hasCustomerIdentifier |
P193786
|
FINISHED |
| Object | Frontier Miles number |
—
|
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: Frontier Miles number | Statement: [Frontier Miles, hasCustomerIdentifier, Frontier Miles number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerIdentifier Context triple: [Frontier Miles, hasCustomerIdentifier, Frontier Miles number]
-
A.
hasCommunicationIdentifier
Indicates that an entity is associated with a specific communication-related identifier (such as a phone number, email address, or messaging handle) used for contact or messaging purposes.
-
B.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
D.
requiresTaxpayerIdentification
Indicates that providing a taxpayer identification number or equivalent tax-related identifier is necessary for the related entity, transaction, or process.
-
E.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 1, 2026, 1:03 a.m.