Triple
T7010579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cockatoo Island |
E162568
|
entity |
| Predicate | hasUNESCOId |
P2117
|
FINISHED |
| Object | 1306 |
—
|
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: 1306 | Statement: [Cockatoo Island, hasUNESCOId, 1306]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNESCOId Context triple: [Cockatoo Island, hasUNESCOId, 1306]
-
A.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
B.
UNESCOWorldHeritageSiteId
chosen
Indicates that an entity is identified as a UNESCO World Heritage Site by a specific UNESCO World Heritage Site identifier.
-
C.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
D.
UNESCOHeritage
Indicates that a place, site, or cultural/natural asset has been officially inscribed on the UNESCO World Heritage List as having outstanding universal value.
-
E.
UNESCOWorldHeritageSiteRelated
Indicates a relationship where one entity is designated as, part of, or otherwise officially associated with a UNESCO World Heritage Site.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc3917c481909a288c3e56630c48 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:34 p.m.