Triple
T9097867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wicken |
E218073
|
entity |
| Predicate | hasNearbyDesignation |
P46042
|
FINISHED |
| Object | one of the oldest wetlands in the United Kingdom |
—
|
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: one of the oldest wetlands in the United Kingdom | Statement: [Wicken, hasNearbyDesignation, one of the oldest wetlands in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyDesignation Context triple: [Wicken, hasNearbyDesignation, one of the oldest wetlands in the United Kingdom]
-
A.
hasDesignationNearby
chosen
Indicates that one entity has a designation (such as a label, title, or marker) located in close physical or contextual proximity to another entity.
-
B.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
E.
namedAfterNearbyPlace
Indicates that an entity’s name is derived from or inspired by a geographically nearby place.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc970f340881909f5551219f151acf |
completed | April 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.