Triple
T1645043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Hierro |
E35560
|
entity |
| Predicate | historicalPrimeMeridian |
P6025
|
FINISHED |
| Object | used as reference meridian before Greenwich |
—
|
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: used as reference meridian before Greenwich | Statement: [El Hierro, historicalPrimeMeridian, used as reference meridian before Greenwich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPrimeMeridian Context triple: [El Hierro, historicalPrimeMeridian, used as reference meridian before Greenwich]
-
A.
referenceMeridian
chosen
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
B.
principalMeridianState
Indicates the association between a principal meridian and the state in which that meridian is officially used or defined.
-
C.
principalMeridianNumber
Indicates the specific identifying number assigned to a principal meridian used as a reference line in a land or coordinate survey system.
-
D.
establishedMeridianDistance
Indicates that one entity has determined or set the longitudinal (meridian) distance relative to another reference entity.
-
E.
timeZoneHistorical
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.