Triple
T26914535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rapi:t |
E677481
|
entity |
| Predicate | stylizationFeature |
P137145
|
FINISHED |
| Object | lowercase 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: lowercase letters | Statement: [rapi:t, stylizationFeature, lowercase letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylizationFeature Context triple: [rapi:t, stylizationFeature, lowercase letters]
-
A.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
B.
stylisticElement
chosen
Indicates a relationship where one entity functions as a stylistic feature, device, or characteristic that shapes the expressive or aesthetic quality of another entity.
-
C.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
-
D.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
E.
notableStyleFeature
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fdd39ec8190aaf1714330459136 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:03 a.m.