Triple
T34200298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Luthuli |
E877359
|
entity |
| Predicate | postNominalForGradeBronze |
P1610
|
FINISHED |
| Object | OL (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: OL (Bronze) | Statement: [Order of Luthuli, postNominalForGradeBronze, OL (Bronze)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postNominalForGradeBronze Context triple: [Order of Luthuli, postNominalForGradeBronze, OL (Bronze)]
-
A.
postNominalCategory
Indicates a classification or type assigned to an entity that is expressed in a post-nominal position (after the name or noun).
-
B.
hasPostNominal
chosen
Indicates that an entity is associated with a post-nominal title, abbreviation, or letters that follow a name to denote qualifications, honors, or status.
-
C.
postNominalLetters
Indicates that a person is associated with specific letters placed after their name to denote qualifications, honors, or professional affiliations.
-
D.
bronzeMedalist
Indicates that an entity finished third in a competition or event, earning the bronze medal.
-
E.
medalFor
Indicates that a medal is awarded to an entity in recognition of a specific achievement, action, or service.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:55 a.m.