Triple
T35138935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundo |
E1014648
|
entity |
| Predicate | hasDiminutiveOrAffectionateUsage |
P456
|
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: [Mundo, hasDiminutiveOrAffectionateUsage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiminutiveOrAffectionateUsage Context triple: [Mundo, hasDiminutiveOrAffectionateUsage, yes]
-
A.
hasDiminutive
chosen
Indicates that one entity is a diminutive form or smaller/affectionate variant of another entity.
-
B.
hasAffectionateUse
Indicates that one entity uses or refers to another in a loving, tender, or emotionally warm manner.
-
C.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
-
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.
usesGentilicFor
Indicates that one entity refers to another using a gentilic (a demonym or term denoting origin, nationality, or regional affiliation).
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:02 p.m.