Triple
T34409473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouse Washes |
E883213
|
entity |
| Predicate | designatedAsSSSIBecauseOf |
P19091
|
FINISHED |
| Object | biological interest |
—
|
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: biological interest | Statement: [Ouse Washes, designatedAsSSSIBecauseOf, biological interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsSSSIBecauseOf Context triple: [Ouse Washes, designatedAsSSSIBecauseOf, biological interest]
-
A.
designationReason
chosen
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
B.
wasDesignatedBy
Indicates that an entity received an official status, role, or label as the result of a formal act or decision performed by another agent or authority.
-
C.
isDesignatedIn
Indicates that an entity is officially assigned, named, or recognized in a specific context, document, or jurisdiction.
-
D.
sideDesignation
Indicates how an entity is classified or labeled with respect to a particular side, position, or alignment within a relationship or context.
-
E.
designationBasedOn
Indicates that one entity’s designation, label, or title is assigned or determined on the basis of another entity or criterion.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:59 a.m.