Triple
T13175675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derry & Toms |
E313091
|
entity |
| Predicate | roofGardensLaterUse |
P99561
|
FINISHED |
| Object | restaurant and event venue |
—
|
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: restaurant and event venue | Statement: [Derry & Toms, roofGardensLaterUse, restaurant and event venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofGardensLaterUse Context triple: [Derry & Toms, roofGardensLaterUse, restaurant and event venue]
-
A.
roofGardenUse
chosen
Indicates that a roof garden is being utilized for a specific function or activity.
-
B.
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.
-
C.
usedTerracing
Indicates that an entity employed terracing techniques, such as creating stepped or leveled surfaces, in carrying out an activity or modifying land.
-
D.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
E.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.