Triple
T19450099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy 1830 ellipsoid |
E486592
|
entity |
| Predicate | authorityCode |
P135938
|
FINISHED |
| Object | EPSG:7001 |
—
|
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: EPSG:7001 | Statement: [Airy 1830 ellipsoid, authorityCode, EPSG:7001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityCode Context triple: [Airy 1830 ellipsoid, authorityCode, EPSG:7001]
-
A.
designationAuthority
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
-
B.
gridCodeAuthority
Indicates that an authority or governing body is responsible for assigning, managing, or validating a specific grid code for an entity or location.
-
C.
areaOfAuthority
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
-
D.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
E.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.