Triple
T28891324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bordelon family |
E732701
|
entity |
| Predicate | narrativeThemes |
P150352
|
FINISHED |
| Object | family legacy |
—
|
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 legacy | Statement: [Bordelon family, narrativeThemes, family legacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeThemes Context triple: [Bordelon family, narrativeThemes, family legacy]
-
A.
narrativeThemeOfWork
Indicates that one concept or motif functions as a central narrative theme within a particular creative work.
-
B.
narrativeMotif
Indicates a recurring thematic element, pattern, or situation that appears across one or more narratives and helps structure or convey their underlying meanings.
-
C.
primaryStoryThemes
chosen
Indicates the main recurring ideas or motifs that characterize and unify a story’s narrative.
-
D.
narrativeThemeInvolvement
Indicates that an entity participates in or contributes to a particular narrative theme within a story or discourse.
-
E.
fictionalTheme
Indicates that a work, element, or context is centered around or characterized by a fictional theme or motif.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 7:55 a.m.