Triple
T29847561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China Doll |
E757970
|
entity |
| Predicate | hasStorytellingStyle |
P5869
|
FINISHED |
| Object | intense |
—
|
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: intense | Statement: [China Doll, hasStorytellingStyle, intense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorytellingStyle Context triple: [China Doll, hasStorytellingStyle, intense]
-
A.
usesNarrativeStyle
Indicates that one entity employs or adopts a particular narrative style in presenting or structuring content or information.
-
B.
narrativeStyle
chosen
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
C.
hasSpeakingStyle
Indicates that one entity exhibits or is characterized by a particular manner or style of speaking in relation to another entity.
-
D.
modeOfTelling
Indicates the manner or medium through which something is narrated, communicated, or expressed.
-
E.
hasDramaticStyle
Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 29, 2026, 5:42 p.m.