Triple
T31081847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainham |
E792117
|
entity |
| Predicate | natureReserve |
P46488
|
FINISHED |
| Object | RSPB Rainham Marshes |
—
|
NE NERFINISHED |
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: RSPB Rainham Marshes | Statement: [Rainham, natureReserve, RSPB Rainham Marshes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureReserve Context triple: [Rainham, natureReserve, RSPB Rainham Marshes]
-
A.
natureReserveSince
Indicates that an area has held the legal or official status of a nature reserve since a specified point in time.
-
B.
containsNatureReserve
chosen
Indicates that one entity geographically includes or encompasses a designated nature reserve within its boundaries.
-
C.
ecologicalReserveType
Indicates the specific category or classification of an ecological reserve associated with an entity.
-
D.
territorialNature
Indicates a tendency of an entity to defend or assert control over a specific area or domain against others.
-
E.
designatedStrictNatureReserve
Indicates that an entity has been formally designated as a strict nature reserve, typically granting it the highest level of legal protection for conservation purposes.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 9:02 p.m.