Triple
T14613537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OnePass |
E343019
|
entity |
| Predicate | eliteTierExample |
P20239
|
FINISHED |
| Object | Silver Elite |
—
|
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: Silver Elite | Statement: [OnePass, eliteTierExample, Silver Elite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteTierExample Context triple: [OnePass, eliteTierExample, Silver Elite]
-
A.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
-
B.
topTierProfessional
Indicates that an entity is recognized as a highly skilled, elite-level professional within its field or domain.
-
C.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
D.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
E.
elite
chosen
Indicates that the subject belongs to a select, superior, or highly privileged subset within a larger group or category.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb45264988190a1df13e8b54a85bd |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.