Triple
T28515775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ola Prime |
E721612
|
entity |
| Predicate | categoryTier |
P157883
|
FINISHED |
| Object | above economy |
—
|
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 economy | Statement: [Ola Prime, categoryTier, above economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryTier Context triple: [Ola Prime, categoryTier, above economy]
-
A.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
B.
tierInRegion
Indicates that an entity is assigned to a specific tier or level within a given region or geographic area.
-
C.
categoryAbove
chosen
Indicates that one category is positioned higher than another in a hierarchy, ranking, or ordered structure.
-
D.
tierDeterminedBy
Indicates that the classification level or rank of one entity is decided or derived based on the properties, status, or outcome associated with another entity.
-
E.
eliteTierSystem
Indicates a relationship where entities are organized or classified into higher, privileged levels within a tiered ranking or status 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 3:17 a.m.