Triple
T15633746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Edward’s Church, Stow-on-the-Wold |
E375883
|
entity |
| Predicate | hasYewTrees |
P6742
|
FINISHED |
| Object | ancient yew trees flanking the north door |
—
|
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: ancient yew trees flanking the north door | Statement: [St Edward’s Church, Stow-on-the-Wold, hasYewTrees, ancient yew trees flanking the north door]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYewTrees Context triple: [St Edward’s Church, Stow-on-the-Wold, hasYewTrees, ancient yew trees flanking the north door]
-
A.
hasTrees
chosen
Indicates that something possesses or contains one or more trees.
-
B.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
C.
numberOfTrees
Indicates the count or quantity of trees associated with a given entity or context.
-
D.
hasTreeCanopyProtection
Indicates that an entity is subject to rules or measures that preserve, limit removal of, or otherwise protect the tree canopy associated with it.
-
E.
hasTree
Indicates that one entity possesses, contains, or is associated with a tree.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb7338881909f3c430bb73f91d1 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.