Triple
T17051441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outstanding Innovation Award from IBM |
E413705
|
entity |
| Predicate | isCorporateHonor |
P92060
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Outstanding Innovation Award from IBM, isCorporateHonor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCorporateHonor Context triple: [Outstanding Innovation Award from IBM, isCorporateHonor, true]
-
A.
isHonor
chosen
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
B.
isMajorCompanyIn
Indicates that a company is a leading or dominant business entity within a specified country, region, or market.
-
C.
isPrivateCompany
Indicates that an entity operates as a privately held company, not publicly traded on a stock exchange.
-
D.
isHonorSocietyFor
Indicates that an organization functions as an honor society specifically recognizing and serving the members of a particular group or field.
-
E.
isHonorificOffice
Indicates that a given office or position is honorary in nature, typically carrying prestige or ceremonial status rather than substantive powers or duties.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa26e84819098b41ae15618e813 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.