Triple
T22472037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amy Archer |
E555524
|
entity |
| Predicate | worksOnStoryAbout |
P148337
|
FINISHED |
| Object | rise of Norville Barnes |
—
|
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: rise of Norville Barnes | Statement: [Amy Archer, worksOnStoryAbout, rise of Norville Barnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnStoryAbout Context triple: [Amy Archer, worksOnStoryAbout, rise of Norville Barnes]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
worksForInNovel
Indicates that one entity is employed by or serves another entity within the fictional context of a specific novel.
-
C.
tellsStoriesIn
Indicates that one entity narrates or recounts stories within or to the context of another entity (such as a place, group, or medium).
-
D.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
worksAgainst
Indicates that one entity actively opposes, counteracts, or undermines the goals, effects, or interests of another entity.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be0d3c08190851537660cda619c |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:48 p.m.