Triple
T31645229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabhi |
E807567
|
entity |
| Predicate | usesShadja |
P155983
|
FINISHED |
| Object | S |
—
|
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: S | Statement: [Arabhi, usesShadja, S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesShadja Context triple: [Arabhi, usesShadja, S]
-
A.
usesKunya
Indicates that one entity refers to or identifies another entity by a kunya (a teknonymic nickname, typically based on "father/mother of" someone).
-
B.
usesNisba
Indicates that one entity forms or applies a nisba (a relational or adjectival form, often derived from a name or place) to or in relation to another entity.
-
C.
usesSwaras
chosen
Indicates that one entity employs or incorporates specific musical notes (swaras) in relation to another entity or context.
-
D.
hasShiaSubtradition
Indicates that an entity follows, belongs to, or is characterized by a specific subtradition within Shia Islam.
-
E.
usesKakaliNishada
Indicates that one entity employs or incorporates the specific musical element or note known as Kakali Nishada in relation to another entity or context.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 30, 2026, 10:50 p.m.