Triple
T13711997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Needles Lighthouse |
E328793
|
entity |
| Predicate | nearbyGeologicalFeature |
P52075
|
FINISHED |
| Object | chalk stacks known as The Needles |
—
|
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: chalk stacks known as The Needles | Statement: [Needles Lighthouse, nearbyGeologicalFeature, chalk stacks known as The Needles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyGeologicalFeature Context triple: [Needles Lighthouse, nearbyGeologicalFeature, chalk stacks known as The Needles]
-
A.
nearGeologicalSite
chosen
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
B.
shareGeologicalFeature
Indicates that two or more entities have a geological feature in common, such as sharing the same type, structure, or formation.
-
C.
nearbyFeature
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
D.
nearbyBasin
Indicates that one basin is located close to another basin in space.
-
E.
nearbyMountainRegion
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd4395e8c0819098719c8cd344aa33 |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.