Triple
T12196136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outback New South Wales |
E290588
|
entity |
| Predicate | primaryResources |
P2856
|
FINISHED |
| Object | silver |
—
|
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: silver | Statement: [Outback New South Wales, primaryResources, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResources Context triple: [Outback New South Wales, primaryResources, silver]
-
A.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
B.
traditionalResource
Indicates that one entity is a resource or practice that has been passed down through tradition and is recognized as part of a longstanding cultural or customary system used by another entity.
-
C.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
D.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
E.
naturalResources
chosen
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.