Triple
T34880549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Beetson |
E1005997
|
entity |
| Predicate | heritageNumberForAustralia |
P192321
|
FINISHED |
| Object | 450 |
—
|
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: 450 | Statement: [Arthur Beetson, heritageNumberForAustralia, 450]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageNumberForAustralia Context triple: [Arthur Beetson, heritageNumberForAustralia, 450]
-
A.
builtHeritage
Indicates a relationship where a structure or site is recognized as part of the historically or culturally significant built environment.
-
B.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
C.
heritageId
Indicates that one entity serves as the heritage identifier or heritage reference code associated with another entity.
-
D.
heritageStatusOf
Indicates that one entity holds a particular heritage designation or protection status in relation to another entity (such as a site, object, or tradition).
-
E.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: May 3, 2026, 4 p.m.