Triple
T20325616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugar Hill |
E492326
|
entity |
| Predicate | exploresThemeThroughCharacter |
P30025
|
FINISHED |
| Object | family via Lolly Jonas |
—
|
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 via Lolly Jonas | Statement: [Sugar Hill, exploresThemeThroughCharacter, family via Lolly Jonas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresThemeThroughCharacter Context triple: [Sugar Hill, exploresThemeThroughCharacter, family via Lolly Jonas]
-
A.
thematicCharacter
Indicates that an entity serves as a central or recurring figure embodying key themes or motifs within a narrative or discourse.
-
B.
themeInvolvingCharacter
chosen
Indicates that a theme, motif, or abstract concept centrally involves or is significantly shaped by a particular character.
-
C.
characterTheme
Indicates that a particular theme, motif, or conceptual focus is associated with a given character.
-
D.
investigatesCharacter
Indicates that one entity conducts an inquiry or examination into another entity’s actions, background, or role.
-
E.
mainThemeCharacter
Indicates that a character serves as the central or primary figure associated with the main theme of a work or narrative.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778f20288190b1862d6be61bfb67 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.