Triple
T13983317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pura Belpré Award |
E336368
|
entity |
| Predicate | awardedForCommunity |
P112040
|
FINISHED |
| Object | Latino community |
—
|
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: Latino community | Statement: [Pura Belpré Award, awardedForCommunity, Latino community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForCommunity Context triple: [Pura Belpré Award, awardedForCommunity, Latino community]
-
A.
celebratedByCommunity
Indicates that an event, person, or achievement is honored, recognized, or joyfully acknowledged by a community.
-
B.
acceptedByCommunity
Indicates that something has been approved, endorsed, or generally recognized as valid or appropriate by a particular community.
-
C.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
D.
builtForCommunity
Indicates that something was created or designed with the primary purpose of serving, benefiting, or being used by a particular community.
-
E.
awardedFrom
Indicates that one entity has received an award, prize, or honor that originates from or is granted by another entity.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea2e8808190a1203a6386224bd8 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:18 p.m.