Triple
T24413778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Malkauns |
E615524
|
entity |
| Predicate | characteristicPhrase |
P132994
|
FINISHED |
| Object | g M d n d M g |
—
|
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: g M d n d M g | Statement: [Raga Malkauns, characteristicPhrase, g M d n d M g]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicPhrase Context triple: [Raga Malkauns, characteristicPhrase, g M d n d M g]
-
A.
typicalPhrase
chosen
Indicates that the object is a phrase commonly or characteristically used in connection with the subject.
-
B.
featuresCatchphrase
Indicates that an entity prominently includes or is associated with a particular catchphrase.
-
C.
symbolicPhrase
Indicates a relationship where one entity is represented or expressed by a symbolic phrase associated with another entity.
-
D.
mainPhrase
Indicates that the referenced phrase functions as the primary or central phrase within a larger linguistic or structural unit.
-
E.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958302ec8190bf32409a5ca00ebf |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:12 a.m.