Triple
T24559432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agra gharana |
E607610
|
entity |
| Predicate | hasNotableExponent |
P29301
|
FINISHED |
| Object | Faiyaz Khan |
—
|
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: Faiyaz Khan | Statement: [Agra gharana, hasNotableExponent, Faiyaz Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableExponent Context triple: [Agra gharana, hasNotableExponent, Faiyaz Khan]
-
A.
notableExponents
chosen
Indicates that certain entities are especially prominent, influential, or exemplary practitioners or representatives of a given field, movement, or activity.
-
B.
hasExponentialFactor
Indicates that one entity serves as an exponential factor or exponent applied to another entity in a mathematical or computational expression.
-
C.
hasExponentGroup
Indicates that one entity is associated with, or belongs to, a particular exponent group in a mathematical or algebraic context.
-
D.
allowsExponentType
Indicates that one entity permits or supports the use of a specified type for an exponent in an operation or expression.
-
E.
hasSignificantFigure
Indicates that an entity is associated with a person who plays an important or influential role in relation to it.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f4af6481908576473adab9f6bf |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.