Triple
T37207220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshwari sarees |
E922203
|
entity |
| Predicate | hasSeasonalSuitability |
P121771
|
FINISHED |
| Object | summer wear |
—
|
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: summer wear | Statement: [Maheshwari sarees, hasSeasonalSuitability, summer wear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalSuitability Context triple: [Maheshwari sarees, hasSeasonalSuitability, summer wear]
-
A.
basedOnSeason
Indicates that something is determined, influenced, or derived according to a particular season or time of year.
-
B.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
C.
seasonalValidity
chosen
Indicates that something is valid, applicable, or in effect only during a specific season or set of seasons.
-
D.
isSeasonalStandard
Indicates that something follows or conforms to the standard conditions, rules, or patterns that apply only during a specific season or time period.
-
E.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:15 p.m.