Triple
T6892476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pama–Nyungan languages |
E159080
|
entity |
| Predicate | arealExtent |
P8868
|
FINISHED |
| Object | most of the Australian continent |
—
|
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: most of the Australian continent | Statement: [Pama–Nyungan languages, arealExtent, most of the Australian continent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arealExtent Context triple: [Pama–Nyungan languages, arealExtent, most of the Australian continent]
-
A.
territorialExtent
chosen
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
B.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
-
C.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
D.
peakTerritorialExtent
Indicates the maximum geographic area or territorial size that an entity controlled or occupied at the height of its expansion.
-
E.
maximumExtent
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d930ab548190953291d63cbc721b |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.