Triple
T32057931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosham |
E818669
|
entity |
| Predicate | positionRelativeToPortsmouth |
P197667
|
FINISHED |
| Object | northern part of Portsmouth |
—
|
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: northern part of Portsmouth | Statement: [Cosham, positionRelativeToPortsmouth, northern part of Portsmouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToPortsmouth Context triple: [Cosham, positionRelativeToPortsmouth, northern part of Portsmouth]
-
A.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
B.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
C.
locationRelativeToRichmond
Indicates the spatial or geographic position of one place in relation to the reference location Richmond.
-
D.
positionRelativeToTide
Indicates the spatial relationship of something’s location with respect to the current or expected tide level or tidal zone.
-
E.
positionRelativeToCanaryWharf
Indicates the spatial or locational relationship of an entity with respect to Canary Wharf.
- F. None of above. chosen
Provenance (4 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 1, 2026, 12:21 a.m.