Triple
T29993205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What He Wrote |
E761938
|
entity |
| Predicate | hasTypeOfStorytelling |
P11858
|
FINISHED |
| Object | character-based narrative |
—
|
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: character-based narrative | Statement: [What He Wrote, hasTypeOfStorytelling, character-based narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfStorytelling Context triple: [What He Wrote, hasTypeOfStorytelling, character-based narrative]
-
A.
hasStorylineType
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
B.
hasFolkTaleType
Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
-
C.
modeOfTelling
Indicates the manner or medium through which something is narrated, communicated, or expressed.
-
D.
narrativeType
chosen
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
E.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 29, 2026, 6:39 p.m.