Triple
T19399267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wood-Pile |
E485272
|
entity |
| Predicate | authorStyleFeature |
P27486
|
FINISHED |
| Object | colloquial diction |
—
|
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: colloquial diction | Statement: [The Wood-Pile, authorStyleFeature, colloquial diction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorStyleFeature Context triple: [The Wood-Pile, authorStyleFeature, colloquial diction]
-
A.
authorStyle
chosen
Indicates the stylistic characteristics or manner of expression associated with a particular author in their works.
-
B.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
C.
authorOfStyle
Indicates that an entity is the creator or originator of a particular style, method, or artistic approach.
-
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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62575d78881909c2cfee799859261 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.