Triple
T12642716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gooniyandi people |
E301937
|
entity |
| Predicate | haveCustomaryLaw |
P9797
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gooniyandi people, haveCustomaryLaw, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCustomaryLaw Context triple: [Gooniyandi people, haveCustomaryLaw, yes]
-
A.
customaryLaw
chosen
Indicates that a relationship, behavior, or rule is governed by unwritten, traditional norms and practices recognized as binding within a community or group.
-
B.
haveCivilLaw
Indicates that an entity is subject to, governed by, or operates under a civil law legal system.
-
C.
hasOwnCanonLawParticularLaw
Indicates that an entity possesses its own specific set of canon or particular laws distinct from general or universal church law.
-
D.
hasExtendedLawSystem
Indicates that an entity possesses a comprehensive, detailed, and well-developed system of laws or legal regulations.
-
E.
separateLegalSystem
Indicates that one entity maintains its own distinct and independent legal system from 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:17 p.m.