Triple
T4701039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonnarua people |
E104269
|
entity |
| Predicate | hasOngoingActivity |
P13923
|
FINISHED |
| Object | land rights claims in Hunter Valley |
—
|
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: land rights claims in Hunter Valley | Statement: [Wonnarua people, hasOngoingActivity, land rights claims in Hunter Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOngoingActivity Context triple: [Wonnarua people, hasOngoingActivity, land rights claims in Hunter Valley]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasActivityStatus
chosen
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
C.
isOngoing
Indicates that an action, process, or state is currently in progress and has not yet been completed or concluded.
-
D.
hasContemporaryActivity
Indicates that two activities occur during the same time period or overlap in time.
-
E.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.