Triple
T14480194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Dress A |
E359081
|
entity |
| Predicate | hasDesignStatus |
P43407
|
FINISHED |
| Object | individually recognized piece |
—
|
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: individually recognized piece | Statement: [Blue Dress A, hasDesignStatus, individually recognized piece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignStatus Context triple: [Blue Dress A, hasDesignStatus, individually recognized piece]
-
A.
designStatus
chosen
Indicates the current state or phase of progress for a design within its lifecycle.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
hasDesigned
Indicates that one entity is the creator or designer of another entity.
-
D.
hasDesignAuthority
Indicates that one entity holds the recognized power or responsibility to make or approve design decisions affecting another entity.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924a576c819098351efabdb779b1 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.