Triple
T21606419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Garden |
E533184
|
entity |
| Predicate | hasSurroundingInfrastructure |
P124983
|
FINISHED |
| Object | roads |
—
|
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: roads | Statement: [Middle Garden, hasSurroundingInfrastructure, roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingInfrastructure Context triple: [Middle Garden, hasSurroundingInfrastructure, roads]
-
A.
hasNearbyInfrastructureType
chosen
Indicates that an entity is located close to infrastructure of a specified type.
-
B.
hasCommercialInfrastructure
Indicates that an entity possesses or is equipped with facilities, systems, or structures that support commercial or business activities.
-
C.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
D.
hasInfrastructureAlong
Indicates that infrastructure is present or extends along the length or course of another entity (such as a route, boundary, or geographic feature).
-
E.
adjacentToInfrastructure
Indicates that one entity is located directly next to or in immediate proximity to a piece of infrastructure.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e5783481909db36c388f3ae227 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.