Triple
T7228203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crozon Peninsula |
E154835
|
entity |
| Predicate | notableCliffSite |
P46334
|
FINISHED |
| Object | Tas de Pois (rock stacks at Pen-Hir) |
—
|
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: Tas de Pois (rock stacks at Pen-Hir) | Statement: [Crozon Peninsula, notableCliffSite, Tas de Pois (rock stacks at Pen-Hir)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCliffSite Context triple: [Crozon Peninsula, notableCliffSite, Tas de Pois (rock stacks at Pen-Hir)]
-
A.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
B.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
notableGorge
Indicates a relationship where a gorge is recognized as notable, significant, or of particular interest in some context.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9df72cc81908d1c04e6e310fbb4 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.