Triple
T8198226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-y-a-n |
E191489
|
entity |
| Predicate | hasHyphenationStyle |
P64072
|
FINISHED |
| Object | stylized with hyphens between letters |
—
|
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: stylized with hyphens between letters | Statement: [R-y-a-n, hasHyphenationStyle, stylized with hyphens between letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHyphenationStyle Context triple: [R-y-a-n, hasHyphenationStyle, stylized with hyphens between letters]
-
A.
hasHyphenation
chosen
Indicates that one entity specifies or provides the hyphenated form or hyphenation pattern of another entity.
-
B.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
-
C.
hasPunctuationSystem
Indicates that an entity possesses or employs a system of punctuation marks for structuring written language.
-
D.
hasStructuralStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular architectural or structural design style.
-
E.
hasHyphenatedIdentity
Indicates that an entity possesses a compound or dual identity expressed as a hyphenated combination of distinct identity components.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c2341f881908be59c378896e5bc |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.