Triple
T25318703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadigal Country |
E634817
|
entity |
| Predicate | governedByConcept |
P98499
|
FINISHED |
| Object | Aboriginal law and custom |
—
|
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: Aboriginal law and custom | Statement: [Gadigal Country, governedByConcept, Aboriginal law and custom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByConcept Context triple: [Gadigal Country, governedByConcept, Aboriginal law and custom]
-
A.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
B.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
C.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
-
D.
areGovernedBy
chosen
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
E.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 21, 2026, 1:28 p.m.