Triple
T34793757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSGB36 |
E1003013
|
entity |
| Predicate | datumShiftRelativeTo |
P181620
|
FINISHED |
| Object | WGS84 |
—
|
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: WGS84 | Statement: [OSGB36, datumShiftRelativeTo, WGS84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datumShiftRelativeTo Context triple: [OSGB36, datumShiftRelativeTo, WGS84]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
movesRelativeTo
Indicates that one entity changes its position or orientation with respect to another entity, rather than with respect to a fixed reference frame.
-
C.
marksShiftToward
Indicates a change or transition from one state, condition, or position toward another, highlighting the direction or trend of that shift.
-
D.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
E.
relativeToWIT
Indicates a relationship where something is defined, measured, or interpreted in relation to a specific WIT (Work Item Type) as its reference point.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.