Triple
T33319818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GS |
E853107
|
entity |
| Predicate | tierLevelRelativeTo |
P25304
|
FINISHED |
| Object | above Premier 1K |
—
|
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 Premier 1K | Statement: [GS, tierLevelRelativeTo, above Premier 1K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierLevelRelativeTo Context triple: [GS, tierLevelRelativeTo, above Premier 1K]
-
A.
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.
-
B.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
C.
tierRelativeToTopDivision
Indicates the competitive level or rank of a division relative to the highest (top) division in a hierarchy.
-
D.
relativeLevel
chosen
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.