Triple
T3377513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prydonian Chapter |
E71099
|
entity |
| Predicate | dressCodeElement |
P39714
|
FINISHED |
| Object | high-collared ceremonial robes |
—
|
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: high-collared ceremonial robes | Statement: [Prydonian Chapter, dressCodeElement, high-collared ceremonial robes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dressCodeElement Context triple: [Prydonian Chapter, dressCodeElement, high-collared ceremonial robes]
-
A.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
dressFeature
chosen
Indicates that a dress possesses or is characterized by a particular feature, attribute, or design element.
-
C.
dressRecommendation
Indicates a suggested or advised choice of dress for a particular person and/or occasion.
-
D.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
E.
wardrobeFeature
Indicates that a wardrobe possesses or includes a specific feature, attribute, or functional element.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.