Triple
T30125628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wapping Police Station |
E765686
|
entity |
| Predicate | isRiversideFacility |
P145512
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wapping Police Station, isRiversideFacility, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRiversideFacility Context triple: [Wapping Police Station, isRiversideFacility, true]
-
A.
isRiverside
Indicates that one entity is located beside or along the bank of a river in relation to another entity.
-
B.
isRiversideRangeOf
Indicates that something is a range or stretch of land that lies along the side of a river.
-
C.
isWaterfrontFacility
chosen
Indicates that a facility is located directly on or adjacent to a body of water, providing waterfront access or frontage.
-
D.
isWaterfrontFacilityType
Indicates that a facility is classified as a type specifically associated with or located on a waterfront.
-
E.
isFacilityOf
Indicates that a facility (such as a building, site, or infrastructure) belongs to, is operated by, or is associated with a particular organization, entity, or system.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67def29e4819089a24fac521054f6 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:14 p.m.