Triple
T14613536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OnePass |
E343019
|
entity |
| Predicate | statusLevels |
P94017
|
FINISHED |
| Object | Elite tiers |
—
|
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: Elite tiers | Statement: [OnePass, statusLevels, Elite tiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusLevels Context triple: [OnePass, statusLevels, Elite tiers]
-
A.
statusLevelBasedOn
Indicates that one entity’s status level is determined or derived from another specified factor or entity.
-
B.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
-
C.
statusLevelWithinProgram
chosen
Indicates the relative rank or standing an entity holds within a specific program.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb45264988190a1df13e8b54a85bd |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.