Triple
T11859246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dior wordmark |
E282116
|
entity |
| Predicate | scriptCase |
P75392
|
FINISHED |
| Object | capital D with lowercase ior |
—
|
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: capital D with lowercase ior | Statement: [Dior wordmark, scriptCase, capital D with lowercase ior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCase Context triple: [Dior wordmark, scriptCase, capital D with lowercase ior]
-
A.
scriptCodeCase
chosen
Indicates how the script code is represented with respect to letter casing (e.g., uppercase, lowercase, or mixed case).
-
B.
scriptSystem
Indicates that one entity is the scripting or programming system used to control, configure, or automate the behavior of another entity.
-
C.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
D.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
-
E.
scriptCategory
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69a099c8190a674db64c50eca5a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.