Triple
T28518397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haven, Maine |
E721687
|
entity |
| Predicate | hasReputationInFandom |
P195559
|
FINISHED |
| Object | cursed town |
—
|
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: cursed town | Statement: [Haven, Maine, hasReputationInFandom, cursed town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationInFandom Context triple: [Haven, Maine, hasReputationInFandom, cursed town]
-
A.
hasFandomReputationAs
chosen
Indicates that an entity is widely regarded or characterized in a particular way within a specific fandom or fan community.
-
B.
hasInUniverseReputation
Indicates that an entity holds a particular level or type of reputation within a specified fictional or conceptual universe.
-
C.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
E.
hasNotableReputation
Indicates that an entity is widely recognized or distinguished for a particular quality, achievement, or characteristic.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: April 28, 2026, 3:19 a.m.