Triple
T12775296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Hilarius |
E305351
|
entity |
| Predicate | authorStyleContext |
P27486
|
FINISHED |
| Object | postmodernism |
—
|
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: postmodernism | Statement: [Dr. Hilarius, authorStyleContext, postmodernism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorStyleContext Context triple: [Dr. Hilarius, authorStyleContext, postmodernism]
-
A.
authorStyle
chosen
Indicates the stylistic characteristics or manner of expression associated with a particular author in their works.
-
B.
styleContext
Indicates that one entity provides the stylistic or formatting context within which another entity is interpreted or rendered.
-
C.
editingStyle
Indicates the characteristic manner or approach used when revising, arranging, or refining content.
-
D.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
E.
compositionStyle
Indicates the characteristic manner or approach in which something is composed, such as its structural, aesthetic, or stylistic conventions.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df6b3c88190b0bbe70de8ddcbf3 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.