Triple
T14288818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papunya |
E354252
|
entity |
| Predicate | hasOutstations |
P113639
|
FINISHED |
| Object | nearby smaller homelands |
—
|
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: nearby smaller homelands | Statement: [Papunya, hasOutstations, nearby smaller homelands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutstations Context triple: [Papunya, hasOutstations, nearby smaller homelands]
-
A.
hasFocalStations
Indicates that an entity is associated with one or more primary or central stations that serve as its main points of focus or operation.
-
B.
hasStations
Indicates that one entity possesses, contains, or is associated with one or more stations.
-
C.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
D.
hasDedicatedStations
Indicates that specific stations are exclusively assigned or reserved for a particular entity or purpose.
-
E.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de698023288190b1d705235c2b2ca3 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.