Triple
T28905097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze Clio |
E733050
|
entity |
| Predicate | rankWithinProgram |
P34755
|
FINISHED |
| Object | non-top tier |
—
|
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: non-top tier | Statement: [Bronze Clio, rankWithinProgram, non-top tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinProgram Context triple: [Bronze Clio, rankWithinProgram, non-top tier]
-
A.
rankWithinOrganization
Indicates the relative hierarchical position or level an entity holds within a specific organization.
-
B.
classRank
Indicates the relative academic standing or position of an entity within a class or cohort based on performance or criteria.
-
C.
attendanceRank
Indicates the relative position or level of an entity in terms of how frequently or consistently it attends compared to others.
-
D.
rankingAtCompletion
Indicates the position or rank an entity holds in an ordered list or competition at the moment the relevant process or event is completed.
-
E.
rankStatus
chosen
Indicates the hierarchical level or position an entity holds within an ordered 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ada0060819098ff14053a958b64 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:06 a.m.