Triple
T26310364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mondrian dress |
E661803
|
entity |
| Predicate | neckline |
P49300
|
FINISHED |
| Object | round neckline |
—
|
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: round neckline | Statement: [Mondrian dress, neckline, round neckline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckline Context triple: [Mondrian dress, neckline, round neckline]
-
A.
neckCharacteristic
chosen
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
B.
neckDiameter
Indicates the width or thickness of an object's neck portion, typically measured as the diameter across that narrowed section.
-
C.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
D.
neckLengthComparedTo
Indicates a comparison of the length of one entity’s neck relative to another entity’s neck.
-
E.
typicalShoulderLine
Indicates that one entity has a shoulder line that is characteristic or standard for the type, style, or category represented by the other entity.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee7e6348190951e6f9647f5555b |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:21 p.m.