Triple
T17334262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorer (Flying Blue tier) |
E420893
|
entity |
| Predicate | targetMemberType |
P121
|
FINISHED |
| Object | new traveler |
—
|
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: new traveler | Statement: [Explorer (Flying Blue tier), targetMemberType, new traveler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetMemberType Context triple: [Explorer (Flying Blue tier), targetMemberType, new traveler]
-
A.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
B.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
hasAlternateMemberType
Indicates that an entity is associated with a different or substitute type of member than its primary or standard member type.
-
E.
parentType
Indicates that one entity serves as the direct parent or higher-level type from which another entity is derived or classified.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a106df48190a50f96febc13cde7 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.