Triple
T32829645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Empty Man |
E839651
|
entity |
| Predicate | hasUrbanLegend |
P77935
|
FINISHED |
| Object | The Empty Man entity |
—
|
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: The Empty Man entity | Statement: [The Empty Man, hasUrbanLegend, The Empty Man entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanLegend Context triple: [The Empty Man, hasUrbanLegend, The Empty Man entity]
-
A.
associatedWithUrbanLegend
chosen
Indicates a relationship where something is connected to, derived from, or commonly regarded as part of an urban legend.
-
B.
hasCultOrLegend
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
-
C.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
-
D.
hasSuperstition
Indicates that one entity holds or practices a particular superstition related to another entity or concept.
-
E.
hasUrbanFeature
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:16 a.m.