Triple
T34114157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tjilbruke spring sites |
E874922
|
entity |
| Predicate | hasCustodialGroup |
P20855
|
FINISHED |
| Object | Kaurna traditional owners |
—
|
NE NERFINISHED |
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: Kaurna traditional owners | Statement: [Tjilbruke spring sites, hasCustodialGroup, Kaurna traditional owners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustodialGroup Context triple: [Tjilbruke spring sites, hasCustodialGroup, Kaurna traditional owners]
-
A.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
B.
hasCustodyRole
chosen
Indicates that one entity holds a specific custodial responsibility or role in relation to another entity.
-
C.
hasSubsidiaryRoleInGroup
Indicates that an entity holds a secondary or supporting role within a specified group.
-
D.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
E.
hasGroupMember
Indicates that a group or collection includes a specific entity as one of its members.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:53 a.m.