Triple
T26617316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clanton, Mississippi |
E668095
|
entity |
| Predicate | hasRecurringCharactersFrom |
P120416
|
FINISHED |
| Object | Jake Brigance |
—
|
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: Jake Brigance | Statement: [Clanton, Mississippi, hasRecurringCharactersFrom, Jake Brigance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringCharactersFrom Context triple: [Clanton, Mississippi, hasRecurringCharactersFrom, Jake Brigance]
-
A.
hasRecurringCharacterFrom
chosen
Indicates that one work or series includes a character who also appears recurrently in another work or series.
-
B.
isRecurringCharacter
Indicates that an entity appears repeatedly or regularly within a given narrative, series, or context rather than only once.
-
C.
hasRecurringProtagonists
Indicates that the same main character or set of main characters appears repeatedly across multiple works or installments in a series.
-
D.
hasRecurringSeriesProtagonists
Indicates that a recurring series features one or more protagonists who appear repeatedly across its installments.
-
E.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 27, 2026, 2:19 a.m.