Triple
T37207194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshwari sarees |
E922203
|
entity |
| Predicate | isReversible |
P12913
|
FINISHED |
| Object | sometimes |
—
|
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: sometimes | Statement: [Maheshwari sarees, isReversible, sometimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReversible Context triple: [Maheshwari sarees, isReversible, sometimes]
-
A.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
B.
isUsedToReverse
Indicates that one entity serves the function of undoing, inverting, or changing the direction or effect of another entity or process.
-
C.
reversibility
chosen
Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
-
D.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
-
E.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
- 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_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.