Triple
T32831648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menotti |
E839703
|
entity |
| Predicate | notableInFieldOf |
P39276
|
FINISHED |
| Object | classical music |
—
|
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: classical music | Statement: [Menotti, notableInFieldOf, classical music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInFieldOf Context triple: [Menotti, notableInFieldOf, classical music]
-
A.
borneByNotablePeopleInField
Indicates that something (such as a name, title, or distinction) is carried or held by individuals who are recognized as notable within a particular field.
-
B.
notableContributionField
Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
E.
notableAchiever
Indicates that an entity has achieved notable success, distinction, or recognition in a particular field or domain.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:16 a.m.