Triple
T36913982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father John |
E912992
|
entity |
| Predicate | isPartOfNarrativeSection |
P115876
|
FINISHED |
| Object | Georgia section of Cane |
—
|
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: Georgia section of Cane | Statement: [Father John, isPartOfNarrativeSection, Georgia section of Cane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNarrativeSection Context triple: [Father John, isPartOfNarrativeSection, Georgia section of Cane]
-
A.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
B.
narrativeSectionOf
chosen
Indicates that one text segment functions as a narrative section or component within a larger narrative work or document.
-
C.
narrativeSectionName
Indicates the specific title or label assigned to a section within a narrative or story structure.
-
D.
hasChildInNarrative
Indicates that one entity is depicted as the parent of another entity within a specific story, account, or narrative context.
-
E.
hasTypeInNarrative
Indicates that an entity is assigned a specific type or role within the context of a particular 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:13 p.m.