Triple
T18826546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horton Plains National Park |
E460401
|
entity |
| Predicate | previousProtectionYear |
P106628
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Horton Plains National Park, previousProtectionYear, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousProtectionYear Context triple: [Horton Plains National Park, previousProtectionYear, 1969]
-
A.
previousProtectionStatus
Indicates the protection or security state an entity was in before its current protection status.
-
B.
previousProtectionEstablished
chosen
Indicates that a protective measure or status had already been put in place prior to the current point in time or event.
-
C.
previousEventYear
Indicates that one event occurred in a year that is earlier than the year of another event.
-
D.
pastSettingYear
Indicates that an event, narrative, or situation is set in or associated with a specific year in the past.
-
E.
optionalYearBefore
Indicates that one entity may, but does not necessarily, occur or be valid in a year that precedes the year associated with another entity.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6bec7b08190b040ec8b3693f037 |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.