Triple
T24811266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Optime |
E620792
|
entity |
| Predicate | honoursStatus |
P18368
|
FINISHED |
| Object | honours classification |
—
|
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: honours classification | Statement: [Junior Optime, honoursStatus, honours classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursStatus Context triple: [Junior Optime, honoursStatus, honours classification]
-
A.
honoursPosition
Indicates that one entity holds or is recognized with an honorary or distinguished position in relation to another entity.
-
B.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
-
C.
honoursAchievement
Indicates that one entity formally recognizes and celebrates the notable accomplishment or success of another entity.
-
D.
honoursHolder
Indicates that one entity is the designated recipient or bearer of a particular honour, award, or distinction conferred by another entity.
-
E.
graduatedWithHonors
chosen
Indicates that an entity completed an academic program with a distinction or honors-level achievement according to the institution’s criteria.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.