Triple
T16198492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REDMERCEDES |
E393131
|
entity |
| Predicate | hasTitleStylization |
P81918
|
FINISHED |
| Object | all caps |
—
|
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: all caps | Statement: [REDMERCEDES, hasTitleStylization, all caps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleStylization Context triple: [REDMERCEDES, hasTitleStylization, all caps]
-
A.
titleStylization
chosen
Indicates how the written form of a title is stylistically presented, such as through capitalization, spacing, punctuation, or special formatting.
-
B.
includesTitleStyle
Indicates that one entity incorporates or specifies a particular style or formatting for a title associated with it.
-
C.
hasTitleFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
-
D.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222dc6b1c8190a3d8a6451ed8b95a |
completed | April 17, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.