Triple
T38290203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New-England Folktale |
E1022337
|
entity |
| Predicate | highlightsNarrativeSource |
P190610
|
FINISHED |
| Object | New England folktales |
—
|
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: New England folktales | Statement: [A New-England Folktale, highlightsNarrativeSource, New England folktales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsNarrativeSource Context triple: [A New-England Folktale, highlightsNarrativeSource, New England folktales]
-
A.
highlights
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
B.
highlightsSign
Indicates that one entity visually emphasizes or draws special attention to a sign.
-
C.
highlightsType
Indicates that one entity serves as a representative example or instance of the type or category defined by another entity.
-
D.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
E.
notableFeatureInStory
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.