Triple
T34087382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LBD |
E874208
|
entity |
| Predicate | styleRule |
P179090
|
FINISHED |
| Object | appropriate for many dress codes |
—
|
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: appropriate for many dress codes | Statement: [LBD, styleRule, appropriate for many dress codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleRule Context triple: [LBD, styleRule, appropriate for many dress codes]
-
A.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
B.
styleSegment
Indicates a relationship where one segment is characterized or defined by a particular style or formatting.
-
C.
styleRestriction
Indicates a constraint or limitation imposed on the manner, form, or stylistic way in which something may be expressed, presented, or performed.
-
D.
hasRuleStyle
Indicates that an entity is associated with a particular rule-based style or formatting specification.
-
E.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
- F. None of above. chosen
Provenance (4 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:52 a.m.