Triple
T10551419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incredible Edible Todmorden |
E248955
|
entity |
| Predicate | hasMainSiteType |
P28105
|
FINISHED |
| Object | public spaces |
—
|
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: public spaces | Statement: [Incredible Edible Todmorden, hasMainSiteType, public spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSiteType Context triple: [Incredible Edible Todmorden, hasMainSiteType, public spaces]
-
A.
hasMainSite
Indicates that one entity is designated as the primary or central site associated with another entity.
-
B.
hasMainLocationType
chosen
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
hasCapitalSiteType
Indicates the type or classification of the site that serves as the capital for an entity.
-
E.
hasTypeSiteFor
Indicates that one entity serves as the specific site or location designated for a particular type or category of another entity.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.