Triple
T31370698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaMont Robinson |
E800152
|
entity |
| Predicate | hasHonorCreated |
P192065
|
FINISHED |
| Object | induction honors for R&B artists |
—
|
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: induction honors for R&B artists | Statement: [LaMont Robinson, hasHonorCreated, induction honors for R&B artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorCreated Context triple: [LaMont Robinson, hasHonorCreated, induction honors for R&B artists]
-
A.
hasCodeOfHonor
Indicates that an entity adheres to a personal or shared ethical code that guides its behavior and decisions.
-
B.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
C.
hasPatronHonored
Indicates that a patron is formally recognized or honored in association with another entity, such as an institution, work, or event.
-
D.
hasHonorGuard
Indicates that an entity is accompanied, protected, or ceremonially attended by an honor guard.
-
E.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: April 29, 2026, 9:18 p.m.