Triple
T544847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headless Horseman |
E12709
|
entity |
| Predicate | settingOfLegend |
P1957
|
FINISHED |
| Object | Dutch-settled American village |
—
|
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: Dutch-settled American village | Statement: [Headless Horseman, settingOfLegend, Dutch-settled American village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfLegend Context triple: [Headless Horseman, settingOfLegend, Dutch-settled American village]
-
A.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
B.
hasLegendAssociatedWith
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
C.
setting
chosen
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
D.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
E.
displayRule
Indicates the rule or condition that determines how something should be visually presented or displayed.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498dfec5c81908b76d723b30dc2f0 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.