Triple
T33412175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber Gold |
E855615
|
entity |
| Predicate | statusRelativeToEntryLevel |
P131864
|
FINISHED |
| Object | above entry-level tier |
—
|
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: above entry-level tier | Statement: [Uber Gold, statusRelativeToEntryLevel, above entry-level tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusRelativeToEntryLevel Context triple: [Uber Gold, statusRelativeToEntryLevel, above entry-level tier]
-
A.
designationLevelComparedTo
Indicates how the designation level of one entity compares to the designation level of another entity (e.g., higher, lower, or equal).
-
B.
statusRelativeTo
chosen
Indicates the comparative state or condition of one entity in relation to another at a given point or over a period of time.
-
C.
qualificationLevel
Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
-
D.
careerLevel
Indicates the relative stage or rank of an entity within a defined career or professional progression.
-
E.
statusLevelBasedOn
Indicates that one entity’s status level is determined or derived from another specified factor or entity.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:36 a.m.