Triple
T7312480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerolineas Plus |
E168126
|
entity |
| Predicate | loyaltyObjective |
P57185
|
FINISHED |
| Object | customer retention |
—
|
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: customer retention | Statement: [Aerolineas Plus, loyaltyObjective, customer retention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyObjective Context triple: [Aerolineas Plus, loyaltyObjective, customer retention]
-
A.
loyaltyGoal
chosen
Indicates that one entity has the objective or commitment to remain faithful, supportive, or devoted to another entity or cause.
-
B.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyMechanism
Indicates a mechanism or process through which loyalty is established, maintained, or reinforced between entities.
-
E.
loyaltyDomain
Indicates a relationship where loyalty, allegiance, or steadfast support is directed toward or governed by a particular domain, context, or sphere of influence.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec00fef081909cb9768a70cabd80 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.