Triple
T21316039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Otway National Park |
E525472
|
entity |
| Predicate | previouslyIncludedArea |
P52471
|
FINISHED |
| Object | Otway National Park |
—
|
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: Otway National Park | Statement: [Great Otway National Park, previouslyIncludedArea, Otway National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyIncludedArea Context triple: [Great Otway National Park, previouslyIncludedArea, Otway National Park]
-
A.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
B.
previouslyContainedRegion
Indicates that one region used to spatially contain another region at some earlier time, but does not necessarily do so now.
-
C.
includesAreaClaimedAs
Indicates that one entity encompasses or contains an area that is claimed as belonging to another entity.
-
D.
formerlyIncluded
chosen
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
E.
territoryOriginallyIncluded
Indicates that an earlier or original territorial boundary encompassed the referenced area or 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcfdec08190a6e19c907a544921 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:29 p.m.