Triple
T25715614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue is the entry-level tier |
E644855
|
entity |
| Predicate | statusLevelRelative |
P131864
|
FINISHED |
| Object | Below Bronze |
—
|
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: Below Bronze | Statement: [Blue is the entry-level tier, statusLevelRelative, Below Bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusLevelRelative Context triple: [Blue is the entry-level tier, statusLevelRelative, Below Bronze]
-
A.
statusLevelBasedOn
Indicates that one entity’s status level is determined or derived from another specified factor or entity.
-
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.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
-
D.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
E.
statusLevelWithinProgram
Indicates the relative rank or standing an entity holds within a specific program.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 21, 2026, 9:40 p.m.