Triple
T22946180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardy family universe |
E569879
|
entity |
| Predicate | containsStoryType |
P121234
|
FINISHED |
| Object | family drama |
—
|
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: family drama | Statement: [Hardy family universe, containsStoryType, family drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStoryType Context triple: [Hardy family universe, containsStoryType, family drama]
-
A.
hasStorylineType
chosen
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
B.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
-
C.
hasFolkTaleType
Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
-
D.
hasVariantStoriesIn
Indicates that an entity has alternative or differing narrative versions that occur or are found within a specified context or source.
-
E.
hasStoryPath
Indicates that there exists a defined narrative route or sequence of events connecting one entity to another within a story or interactive experience.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819d2d7881909e6390717ff79df0 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.