Triple
T10519218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowland Tropics gallery |
E248116
|
entity |
| Predicate | usesStructureType |
P35482
|
FINISHED |
| Object | glasshouse |
—
|
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: glasshouse | Statement: [Lowland Tropics gallery, usesStructureType, glasshouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStructureType Context triple: [Lowland Tropics gallery, usesStructureType, glasshouse]
-
A.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
usedStructure
chosen
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
C.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
D.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
E.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dd29b48190aa5b170e2558545c |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.