Triple
T34793779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSGB36 |
E1003013
|
entity |
| Predicate | datumOrigin |
P168345
|
FINISHED |
| Object | near Newlyn, Cornwall (mean sea level) |
—
|
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: near Newlyn, Cornwall (mean sea level) | Statement: [OSGB36, datumOrigin, near Newlyn, Cornwall (mean sea level)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datumOrigin Context triple: [OSGB36, datumOrigin, near Newlyn, Cornwall (mean sea level)]
-
A.
datumUsed
Indicates that a particular piece of data is utilized or referenced in performing an action, process, or relation.
-
B.
coordinateOrigin
Indicates the reference point in space from which a coordinate system’s positions or measurements are defined.
-
C.
geodeticReference
chosen
Indicates a relationship where one spatial or geographic entity is defined, measured, or located with respect to a specific geodetic reference system or datum.
-
D.
centerOfOrigin
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
-
E.
depthOrigin
Indicates the reference point or source location from which the depth of an object or region is measured.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.