Triple
T19027841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Model Village (Bourton-on-the-Water) |
E465655
|
entity |
| Predicate | hasMiniatureOf |
P106178
|
FINISHED |
| Object | shops of Bourton-on-the-Water |
—
|
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: shops of Bourton-on-the-Water | Statement: [Model Village (Bourton-on-the-Water), hasMiniatureOf, shops of Bourton-on-the-Water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiniatureOf Context triple: [Model Village (Bourton-on-the-Water), hasMiniatureOf, shops of Bourton-on-the-Water]
-
A.
hasMiniature
chosen
Indicates that one entity possesses or includes a smaller-scale representation or model of another entity.
-
B.
hasApproximateNumberOfMiniatures
Indicates that an entity is associated with an estimated or non-exact count of miniatures.
-
C.
miniaturizedBy
Indicates that an entity has been made smaller in size or scale by another entity or process.
-
D.
isMinorFigureIn
Indicates that an entity plays a small, secondary, or relatively insignificant role within another entity, such as a work, event, or context.
-
E.
hasDiminutive
Indicates that one entity is a diminutive form or smaller/affectionate variant 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d73dc404819092059e496662d151 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.