Triple
T38290192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New-England Folktale |
E1022337
|
entity |
| Predicate | evokesSettingRegion |
P122369
|
FINISHED |
| Object | New England |
—
|
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: New England | Statement: [A New-England Folktale, evokesSettingRegion, New England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evokesSettingRegion Context triple: [A New-England Folktale, evokesSettingRegion, New England]
-
A.
evokesRegion
chosen
Indicates that one entity elicits, suggests, or brings to mind a particular geographic or spatial region.
-
B.
regionSetting
Indicates that an entity is configured to operate within, or is associated with, a specific geographic or logical region.
-
C.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
D.
controlsRegion
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
-
E.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
- 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_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. |
Created at: May 3, 2026, 4:30 p.m.