Triple
T32394298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Street, Totnes |
E827758
|
entity |
| Predicate | hasVisitorAppeal |
P174874
|
FINISHED |
| Object | historic setting with local shops |
—
|
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: historic setting with local shops | Statement: [High Street, Totnes, hasVisitorAppeal, historic setting with local shops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorAppeal Context triple: [High Street, Totnes, hasVisitorAppeal, historic setting with local shops]
-
A.
visitorAppeal
chosen
Indicates how attractive or appealing something is to visitors, reflecting its ability to draw and engage them.
-
B.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
C.
hasMassAppeal
Indicates that something possesses qualities or characteristics that attract or are appealing to a very large, broad, or general audience.
-
D.
handledAppeals
Indicates that one party has received, reviewed, and taken action on appeals submitted by another party.
-
E.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 12:52 a.m.