Triple
T15635813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of W.A. Mozart as a Child |
E375941
|
entity |
| Predicate | depictsFameStatus |
P27257
|
FINISHED |
| Object | famous composer |
—
|
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: famous composer | Statement: [Portrait of W.A. Mozart as a Child, depictsFameStatus, famous composer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsFameStatus Context triple: [Portrait of W.A. Mozart as a Child, depictsFameStatus, famous composer]
-
A.
fameStatus
chosen
Indicates the level or state of public recognition or renown associated with an entity.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
usesPastFameFor
Indicates that one entity leverages or exploits its previous fame or reputation to gain influence, advantage, or benefit in relation to another entity.
-
D.
depictsNotablePerson
Indicates that one entity visually represents or portrays a person who is considered notable or significant.
-
E.
famousAt
Indicates that an entity is widely known or recognized in a particular place, context, or time.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb8b4c48190b80fea6877483089 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.