Triple
T32644344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anoa'i family |
E834559
|
entity |
| Predicate | hasStorylineStable |
P199128
|
FINISHED |
| Object | The Bloodline |
—
|
NE NERFINISHED |
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: The Bloodline | Statement: [Anoa'i family, hasStorylineStable, The Bloodline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorylineStable Context triple: [Anoa'i family, hasStorylineStable, The Bloodline]
-
A.
hasStorylineBuild
Indicates that one element contributes to or defines the development or structure of another element’s storyline.
-
B.
hasStorylineType
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
C.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
D.
hasNarrativeArcIn
Indicates that an entity’s storyline or narrative progression occurs within or is contained by a specified work, context, or medium.
-
E.
hasVariantStoriesIn
Indicates that an entity has alternative or differing narrative versions that occur or are found within a specified context or source.
- F. None of above. chosen
Provenance (4 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
| PDg | Predicate description generation | batch_69ff21ca6964819088bdf1810b7863f2 |
completed | May 9, 2026, noon |
Created at: May 1, 2026, 1:07 a.m.