Triple
T34409472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouse Washes |
E883213
|
entity |
| Predicate | designatedAsSPABecauseOf |
P34507
|
FINISHED |
| Object | migratory birds |
—
|
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: migratory birds | Statement: [Ouse Washes, designatedAsSPABecauseOf, migratory birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsSPABecauseOf Context triple: [Ouse Washes, designatedAsSPABecauseOf, migratory birds]
-
A.
heritageDesignationReason
chosen
Indicates the reason or justification for which something has been granted a particular heritage designation.
-
B.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
C.
heritageDesignationLocation
Indicates that a location is the officially designated site associated with a particular heritage designation.
-
D.
heritageDesignationSubject
Indicates that a subject has been assigned a particular heritage designation or status.
-
E.
heritageDesignationVia
Indicates that a heritage designation for an entity is conferred, recorded, or derived through a specific intermediary process, source, or mechanism.
- 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_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 1, 2026, 1:59 a.m.