Triple
T34012398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundu |
E872148
|
entity |
| Predicate | foldingStyle |
P48607
|
FINISHED |
| Object | front pleat or fold for ease of movement |
—
|
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: front pleat or fold for ease of movement | Statement: [Mundu, foldingStyle, front pleat or fold for ease of movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foldingStyle Context triple: [Mundu, foldingStyle, front pleat or fold for ease of movement]
-
A.
foldingType
chosen
Indicates the specific manner or configuration in which something is folded or arranged into a folded form.
-
B.
folding
Indicates that one entity bends or doubles another entity (or itself) so that parts of it lie flat against or over each other.
-
C.
bendingStyle
Indicates the manner or technique by which something is bent or flexed.
-
D.
canFold
Indicates that one entity has the ability to be bent or collapsed into a more compact form, typically without breaking.
-
E.
folded
Indicates that an entity has been bent or doubled over onto itself, typically along a line or crease, changing its original flat or extended form.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.