Triple
T23265111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JMB |
E588124
|
entity |
| Predicate | eliteTierBenefit |
P77253
|
FINISHED |
| Object | priority check-in for eligible tiers |
—
|
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: priority check-in for eligible tiers | Statement: [JMB, eliteTierBenefit, priority check-in for eligible tiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteTierBenefit Context triple: [JMB, eliteTierBenefit, priority check-in for eligible tiers]
-
A.
exclusiveBenefit
Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
-
B.
isTopTierBenefit
chosen
Indicates that a benefit belongs to the highest or most premium level within a defined benefit hierarchy or structure.
-
C.
benefitsLevel
Indicates the degree or extent to which one entity gains advantages, support, or positive outcomes from another entity or action.
-
D.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
E.
premiumLevel
Indicates the specific tier or rank of premium status assigned to an entity within a graded or subscription-based system.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:29 p.m.