Triple
T2366419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBE |
E47389
|
entity |
| Predicate | includesHonoraryAwards |
P13060
|
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: [MBE, includesHonoraryAwards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHonoraryAwards Context triple: [MBE, includesHonoraryAwards, yes]
-
A.
includesHonoraryAwardsFor
chosen
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
B.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
C.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
D.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
E.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc749f8e0819094144b9dd9db8790 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.