Triple
T33593566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scalphunters |
E860496
|
entity |
| Predicate | usesStorylines |
P24126
|
FINISHED |
| Object | scripted feuds and rivalries |
—
|
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: scripted feuds and rivalries | Statement: [Scalphunters, usesStorylines, scripted feuds and rivalries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStorylines Context triple: [Scalphunters, usesStorylines, scripted feuds and rivalries]
-
A.
storyline
chosen
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
B.
storylinesInclude
Indicates that certain storylines are contained within, or form part of, a larger narrative or collection of narratives.
-
C.
hasStorylineType
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
D.
storylineReason
Indicates that one event, action, or situation occurs as a narrative cause or justification for another within a storyline.
-
E.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 1:41 a.m.