Triple
T8931216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 1 Service Dress |
E212656
|
entity |
| Predicate | typicalHeaddress |
P10555
|
FINISHED |
| Object | No. 1 Service Dress cap |
—
|
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: No. 1 Service Dress cap | Statement: [No. 1 Service Dress, typicalHeaddress, No. 1 Service Dress cap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeaddress Context triple: [No. 1 Service Dress, typicalHeaddress, No. 1 Service Dress cap]
-
A.
headCovering
chosen
Indicates that one entity serves as a covering or protection for the head of another entity.
-
B.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
C.
traditionalMaskType
Indicates the specific kind or category of traditional mask associated with an entity.
-
D.
haveCeremonialHead
Indicates that one entity serves as the formal or symbolic head or leader of another entity, typically without holding full executive power.
-
E.
headShape
Indicates the characteristic form or contour of an entity’s head.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668cdc0c8190b908fd23cbdef534 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.