Triple
T14480192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Dress A |
E359081
|
entity |
| Predicate | hasNamingScheme |
P95414
|
FINISHED |
| Object | alphabetic variant A |
—
|
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: alphabetic variant A | Statement: [Blue Dress A, hasNamingScheme, alphabetic variant A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamingScheme Context triple: [Blue Dress A, hasNamingScheme, alphabetic variant A]
-
A.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
B.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
C.
designationScheme
chosen
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
D.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
-
E.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924a576c819098351efabdb779b1 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.