Triple
T7295527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian territories |
E164510
|
entity |
| Predicate | includeUninhabitedAreas |
P36006
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Australian territories, includeUninhabitedAreas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeUninhabitedAreas Context triple: [Australian territories, includeUninhabitedAreas, true]
-
A.
includesAreasOff
Indicates that something encompasses or covers areas that are turned off, inactive, or excluded from normal operation.
-
B.
normallyUninhabited
chosen
Indicates that a place or area is generally not occupied or lived in by people under usual conditions.
-
C.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
D.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
E.
includedTribalAreas
Indicates that certain areas are designated as tribal regions and are formally included within a specified jurisdiction, boundary, or administrative scope.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8d0c6c8190b32cd08b9a5d96cc |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.