Triple
T26072897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellington |
E657597
|
entity |
| Predicate | hasNotabilityInField |
P39276
|
FINISHED |
| Object | 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: music | Statement: [Ellington, hasNotabilityInField, music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotabilityInField Context triple: [Ellington, hasNotabilityInField, music]
-
A.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
-
B.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
C.
hasNotabilityLevel
Indicates that an entity possesses a specified degree or rank of prominence, importance, or recognition relative to others.
-
D.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
E.
hasNotabilityBasis
Indicates that the notability or significance of one entity is based on, or derived from, another entity or factor.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 26, 2026, 7:31 p.m.