Triple
T17562875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tresco |
E427734
|
entity |
| Predicate | gardensFoundedFor |
P935
|
FINISHED |
| Object | collection of exotic plants |
—
|
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: collection of exotic plants | Statement: [Tresco, gardensFoundedFor, collection of exotic plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardensFoundedFor Context triple: [Tresco, gardensFoundedFor, collection of exotic plants]
-
A.
gardensBuiltFor
Indicates that one entity (such as a garden or landscaped area) was created or designed specifically for the benefit, use, or purpose of another entity.
-
B.
gardensLocation
Indicates that an entity engages in gardening activities at a specified location.
-
C.
foundedFor
chosen
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
E.
createdAsGarden
Indicates that something was brought into existence or established specifically in the form or function of a garden.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456285c808190953a49e77366d8bd |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.