Triple
T34839807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake St Clair Conservation Park (part) |
E1004309
|
entity |
| Predicate | protectedAreaOf |
P28902
|
FINISHED |
| Object | South Australia |
—
|
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: South Australia | Statement: [Lake St Clair Conservation Park (part), protectedAreaOf, South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedAreaOf Context triple: [Lake St Clair Conservation Park (part), protectedAreaOf, South Australia]
-
A.
protectedAreaCountry
chosen
Indicates that a protected area is located within and legally falls under the jurisdiction of a specific country.
-
B.
areaProtected
Indicates that a specified geographic area is designated and managed as protected, typically restricting certain activities to conserve its natural or cultural resources.
-
C.
protectedAreaName
Indicates the designated name assigned to a protected area.
-
D.
protectedAreaCore
Indicates that an entity lies within the core, most strictly protected zone of a designated protected area.
-
E.
protectedAreaEstablishedBy
Indicates that a protected area was formally created, designated, or brought into legal existence by a specific agent or authority.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.