Triple
T3655724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darumbal People Native Title Claim (QUD6131/1998) |
E77524
|
entity |
| Predicate | determinationDate |
P2232
|
FINISHED |
| Object | 2016-06-21 |
—
|
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: 2016-06-21 | Statement: [Darumbal People Native Title Claim (QUD6131/1998), determinationDate, 2016-06-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinationDate Context triple: [Darumbal People Native Title Claim (QUD6131/1998), determinationDate, 2016-06-21]
-
A.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
B.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
C.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
D.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
E.
depositionDate
Indicates the date on which something (such as a document, sample, or record) was formally submitted, filed, or placed into a repository or system.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.