Triple
T31498493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Design Awards 2021 |
E803611
|
entity |
| Predicate | hasWinnerInCategory Social Impact |
P171836
|
FINISHED |
| Object | Be My Eyes |
—
|
NE NERFINISHED |
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: Be My Eyes | Statement: [Apple Design Awards 2021, hasWinnerInCategory Social Impact, Be My Eyes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinnerInCategory Social Impact Context triple: [Apple Design Awards 2021, hasWinnerInCategory Social Impact, Be My Eyes]
-
A.
hasSocialObjective
Indicates that an entity is associated with or pursues a specific social goal or purpose as part of its activities or mission.
-
B.
sponsorCategoryName
Indicates the classification label or category assigned to a sponsor in a given context.
-
C.
generalClassificationWinner
Indicates that the subject is the overall winner in the general classification or overall standings of a competition or event.
-
D.
didWinCategory
chosen
Indicates that an entity achieved first place or victory in a specified category or classification.
-
E.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 30, 2026, 9:42 p.m.