Triple
T28259220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the little poor man |
E712537
|
entity |
| Predicate | affectionateRenderingOf |
P56896
|
FINISHED |
| Object | Il Poverello |
—
|
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: Il Poverello | Statement: [the little poor man, affectionateRenderingOf, Il Poverello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectionateRenderingOf Context triple: [the little poor man, affectionateRenderingOf, Il Poverello]
-
A.
hasAffectionateUse
Indicates that one entity uses or refers to another in a loving, tender, or emotionally warm manner.
-
B.
hasAffectionateNicknameFor
chosen
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
-
C.
objectOfAffectionFor
Indicates that one entity is the target or recipient of another entity’s romantic or affectionate feelings.
-
D.
affectionateHonorific
Indicates a relationship where one entity addresses or refers to another using a respectful title that also conveys warmth, fondness, or emotional closeness.
-
E.
isBelovedOf
Indicates that one entity is deeply loved, cherished, or held in special affection by another entity.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 11:10 p.m.