Triple
T24327413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peacehaven Meridian Monument |
E613138
|
entity |
| Predicate | locatedOnMeridian |
P6025
|
FINISHED |
| Object | Prime Meridian |
—
|
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: Prime Meridian | Statement: [Peacehaven Meridian Monument, locatedOnMeridian, Prime Meridian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnMeridian Context triple: [Peacehaven Meridian Monument, locatedOnMeridian, Prime Meridian]
-
A.
locatedNearCelestialEquator
Indicates that one celestial object or point lies close to the celestial equator in the sky.
-
B.
referenceMeridian
chosen
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
C.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
-
E.
locatedInEasternHemisphere
Indicates that the subject is geographically situated within the Eastern Hemisphere of the Earth.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292eebf7081908ef50ef331ff88aa |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:54 a.m.