Triple
T38114440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar suit |
E951751
|
entity |
| Predicate | skirtSupport |
P116516
|
FINISHED |
| Object | multiple petticoats |
—
|
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: multiple petticoats | Statement: [Bar suit, skirtSupport, multiple petticoats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skirtSupport Context triple: [Bar suit, skirtSupport, multiple petticoats]
-
A.
hasSkirtType
chosen
Indicates that an entity is associated with or characterized by a specific type or style of skirt.
-
B.
backSupport
Indicates that one entity provides physical or structural support to the back of another entity.
-
C.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
D.
supportingBody
Indicates that one entity serves as a supporting or backing body for another entity, providing endorsement, resources, or structural support.
-
E.
weightSupport
Indicates that one entity bears or carries the physical weight of another, providing structural or mechanical support.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.