Triple
T23283920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Rewards |
E588937
|
entity |
| Predicate | tierName |
P37954
|
FINISHED |
| Object | Gold |
—
|
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: Gold | Statement: [Total Rewards, tierName, Gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierName Context triple: [Total Rewards, tierName, Gold]
-
A.
tierType
Indicates the classification level or rank assigned to an entity within a multi-level or hierarchical system.
-
B.
hasTierName
chosen
Indicates that an entity is associated with a specific tier by its name.
-
C.
tierInRegion
Indicates that an entity is assigned to a specific tier or level within a given region or geographic area.
-
D.
tierConfiguration
Indicates how entities are organized or assigned into different levels or tiers according to a defined configuration or scheme.
-
E.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196454b4c8190a797537ce8912241 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.