Triple
T22129866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reload |
E546878
|
entity |
| Predicate | continuesStylisticShiftFrom |
P111395
|
FINISHED |
| Object | Load |
—
|
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: Load | Statement: [Reload, continuesStylisticShiftFrom, Load]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesStylisticShiftFrom Context triple: [Reload, continuesStylisticShiftFrom, Load]
-
A.
stylisticShiftDirection
Indicates the direction or nature of a change in style from one state, work, or expression to another.
-
B.
marksStylisticShiftFrom
Indicates that one element signals a change in style, tone, or manner relative to another element.
-
C.
stylisticFocus
Indicates a relationship where something is primarily concerned with, emphasizes, or is characterized by a particular style or set of stylistic features.
-
D.
textualContinuity
chosen
Indicates that one text segment continues, follows, or is sequentially connected to another in the flow of discourse or narrative.
-
E.
stylisticRange
Indicates the range or spectrum of styles that characterize or can be applied to something.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129851db8819082d50bbb73670bf6 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.