Triple
T4246603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Bottoms |
E95542
|
entity |
| Predicate | hasTargetBodyType |
P42045
|
FINISHED |
| Object | curvy women |
—
|
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: curvy women | Statement: [Apple Bottoms, hasTargetBodyType, curvy women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetBodyType Context triple: [Apple Bottoms, hasTargetBodyType, curvy women]
-
A.
supportsBodyType
chosen
Indicates that one entity is compatible with, designed for, or can accommodate a specified body type.
-
B.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
C.
presentInBodyType
Indicates that something exists or occurs within a specific type or category of body.
-
D.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
E.
includesTypeOfBody
Indicates that one entity encompasses or contains another entity classified as a specific type of body (e.g., physical, celestial, or organizational body).
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9b64ac81908dc44eaae6829b50 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.