Triple
T15625184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partly Cloudy |
E375659
|
entity |
| Predicate | usesNonverbalStorytelling |
P79220
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Partly Cloudy, usesNonverbalStorytelling, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNonverbalStorytelling Context triple: [Partly Cloudy, usesNonverbalStorytelling, true]
-
A.
nonVerbalIn
Indicates that an entity is present in a location or context without using spoken or written language, relying instead on non-verbal communication or behavior.
-
B.
modeOfTelling
chosen
Indicates the manner or medium through which something is narrated, communicated, or expressed.
-
C.
usesSignLanguage
Indicates that one entity communicates using sign language with or in relation to another entity.
-
D.
usesNarrativeStyle
Indicates that one entity employs or adopts a particular narrative style in presenting or structuring content or information.
-
E.
hasNarrativeDevice
Indicates that one entity employs, contains, or is characterized by a particular narrative device used in storytelling or discourse.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9e5e248190ae54cda1fde51efb |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.