Triple
T30983218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abito apartments, Manchester |
E789442
|
entity |
| Predicate | isInWaterfrontArea |
P89005
|
FINISHED |
| Object | Salford Quays waterfront |
—
|
NE NERFINISHED |
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: Salford Quays waterfront | Statement: [Abito apartments, Manchester, isInWaterfrontArea, Salford Quays waterfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInWaterfrontArea Context triple: [Abito apartments, Manchester, isInWaterfrontArea, Salford Quays waterfront]
-
A.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
B.
locatedInWaterfrontArea
chosen
Indicates that something is situated within a designated waterfront area adjacent to a body of water.
-
C.
isWaterfrontDistrict
Indicates that a district is located directly along a body of water, such as a river, lake, or coastline.
-
D.
hasWaterfrontArea
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
E.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.