Triple
T5244177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloucester Quays |
E118416
|
entity |
| Predicate | hasPublicRealm |
P31591
|
FINISHED |
| Object | waterside promenades |
—
|
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: waterside promenades | Statement: [Gloucester Quays, hasPublicRealm, waterside promenades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicRealm Context triple: [Gloucester Quays, hasPublicRealm, waterside promenades]
-
A.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
B.
hasPublicAddressSystem
Indicates that an entity is equipped with or includes a public address (PA) system for broadcasting audio announcements.
-
C.
hasRealmFunction
Indicates that an entity serves a particular role, purpose, or function within a specified realm, domain, or context.
-
D.
hasPublicAuthorityType
Indicates that an entity possesses a specific type or category of public authority status or role.
-
E.
hasPublicSpaceAlong
chosen
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4fa0ec8190bce3da09aa768726 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.