Triple
T34793772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSGB36 |
E1003013
|
entity |
| Predicate | hasTransformationParametersDefinedBy |
P200391
|
FINISHED |
| Object | EPSG registry |
—
|
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: EPSG registry | Statement: [OSGB36, hasTransformationParametersDefinedBy, EPSG registry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransformationParametersDefinedBy Context triple: [OSGB36, hasTransformationParametersDefinedBy, EPSG registry]
-
A.
hasTransformation
Indicates that one entity changes or is converted into another entity, capturing a transformation process or result.
-
B.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
-
C.
hasTransformationFormula
Indicates that there exists a specific formula or rule that defines how one entity is transformed into another.
-
D.
transformationDefinedWith
Indicates that a transformation is specified or characterized using a particular method, rule set, or defining construct.
-
E.
hasTransformationName
Indicates that an entity is associated with a specific name or label assigned to a transformation it undergoes or represents.
- 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_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
| PDg | Predicate description generation | batch_69ff878e8334819097e3c4bb5ca6ffa5 |
completed | May 9, 2026, 7:14 p.m. |
Created at: May 3, 2026, 3:59 p.m.