Triple
T23265106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JMB |
E588124
|
entity |
| Predicate | eliteTierSystem |
P151596
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [JMB, eliteTierSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteTierSystem Context triple: [JMB, eliteTierSystem, yes]
-
A.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
B.
hadTierSystem
Indicates that an entity implemented or used a structured tier-based system, typically organizing elements into hierarchical levels or ranks.
-
C.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
D.
tierInLeagueSystem
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
-
E.
premiumLevel
Indicates the specific tier or rank of premium status assigned to an entity within a graded or subscription-based system.
- F. None of above. chosen
Provenance (4 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:29 p.m.