Triple
T30147034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 2 Service Dress |
E766283
|
entity |
| Predicate | dressOrderNumber |
P58213
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [No. 2 Service Dress, dressOrderNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dressOrderNumber Context triple: [No. 2 Service Dress, dressOrderNumber, 2]
-
A.
orderNumber
Indicates the unique identifier assigned to a specific order within a transaction or ordering process.
-
B.
orderDisplayed
Indicates that a particular order is currently being shown or presented in a user interface or display context.
-
C.
wearingOrder
Indicates the relative sequence in which items are worn on or over one another (e.g., which garment is worn over or under another).
-
D.
displayOrder
chosen
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
E.
distributionOrder
Indicates the sequence or arrangement in which items or resources are distributed among recipients or locations.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8d025c8190aacc621e932e381e |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:19 p.m.