Triple
T32369111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanksgiving Point Gardens |
E827080
|
entity |
| Predicate | hasPlantCollectionFocus |
P1843
|
FINISHED |
| Object | ornamental 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: ornamental plants | Statement: [Thanksgiving Point Gardens, hasPlantCollectionFocus, ornamental plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlantCollectionFocus Context triple: [Thanksgiving Point Gardens, hasPlantCollectionFocus, ornamental plants]
-
A.
hasNumberOfPlantCollections
Indicates the quantity of distinct plant collections associated with an entity.
-
B.
hasCollectionFocus
chosen
Indicates that something is primarily concerned with, centered on, or directed toward a particular collection or set of items.
-
C.
hasMuseumCollectionFocus
Indicates that a museum collection is primarily centered on, dedicated to, or thematically focused around a particular subject, type of object, or area of interest.
-
D.
hasViewOnPlants
Indicates that an entity holds a particular opinion, perspective, or stance regarding plants.
-
E.
hasHerbarium
Indicates that an entity possesses, is associated with, or maintains a herbarium collection.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 12:50 a.m.