Triple
T21241087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Glasshouse |
E523472
|
entity |
| Predicate | climateTypeHoused |
P51066
|
FINISHED |
| Object | Mediterranean climate 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: Mediterranean climate plants | Statement: [Great Glasshouse, climateTypeHoused, Mediterranean climate plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateTypeHoused Context triple: [Great Glasshouse, climateTypeHoused, Mediterranean climate plants]
-
A.
climateTypeRelative
Indicates a relationship where one entity’s climate type is characterized, classified, or compared in relation to another reference climate type.
-
B.
climateTypeRelativeToIsland
Indicates how the climate of one location compares to or is characterized relative to the climate of a specified island.
-
C.
preferredClimate
chosen
Indicates the type of climate that an entity favors or is most suited to.
-
D.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
E.
nativeToClimate
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic region.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735239f48819091ffe518b1aed2e8 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:47 p.m.