Triple
T34386915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Innes Nature Reserve |
E882578
|
entity |
| Predicate | containsHistoricPeriod |
P202338
|
FINISHED |
| Object | 19th-century estate ruins |
—
|
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: 19th-century estate ruins | Statement: [Lake Innes Nature Reserve, containsHistoricPeriod, 19th-century estate ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHistoricPeriod Context triple: [Lake Innes Nature Reserve, containsHistoricPeriod, 19th-century estate ruins]
-
A.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
B.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
C.
includesHistoricSee
Indicates that something contains or encompasses a historically significant site, feature, or point of interest.
-
D.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
-
E.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
- F. None of above. chosen
Provenance (4 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
| PDg | Predicate description generation | batch_6a00733756848190b94524b42d6edf0a |
completed | May 10, 2026, 11:59 a.m. |
Created at: May 1, 2026, 1:59 a.m.