Triple
T1287080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian National Heritage List |
E27458
|
entity |
| Predicate | includesTypeOfPlace |
P16688
|
FINISHED |
| Object | natural place |
—
|
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: natural place | Statement: [Australian National Heritage List, includesTypeOfPlace, natural place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTypeOfPlace Context triple: [Australian National Heritage List, includesTypeOfPlace, natural place]
-
A.
placeType
chosen
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
B.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
C.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
D.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
E.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d1a5508190b4461df77f560df4 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.