Triple
T4646772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nauvari saree |
E102189
|
entity |
| Predicate | hasModernVariation |
P455
|
FINISHED |
| Object | pre-stitched Nauvari saree |
—
|
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: pre-stitched Nauvari saree | Statement: [Nauvari saree, hasModernVariation, pre-stitched Nauvari saree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernVariation Context triple: [Nauvari saree, hasModernVariation, pre-stitched Nauvari saree]
-
A.
hasModernEditions
Indicates that an original work or text has one or more updated or contemporary published editions.
-
B.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
C.
hasModernFormulationIn
Indicates that something has a contemporary or updated version expressed or formulated within a specified context, framework, or medium.
-
D.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
E.
hasModernSuccessor
Indicates that an entity is followed or replaced by another entity that serves as its modern equivalent or continuation.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.