Triple
T29860641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitmedden |
E758303
|
entity |
| Predicate | hasHistoricGarden |
P12538
|
FINISHED |
| Object | Pitmedden Garden |
—
|
NE NERFINISHED |
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: Pitmedden Garden | Statement: [Pitmedden, hasHistoricGarden, Pitmedden Garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricGarden Context triple: [Pitmedden, hasHistoricGarden, Pitmedden Garden]
-
A.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
B.
hasGardenType
chosen
Indicates that an entity possesses or is associated with a garden of a specified type.
-
C.
hasGardenRelation
Indicates a relationship in which one entity is associated with another through the presence, ownership, or inclusion of a garden.
-
D.
hasGardenSquare
Indicates that an entity includes, is adjacent to, or is otherwise associated with a garden square.
-
E.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 29, 2026, 5:49 p.m.