Triple
T24793235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madura cultural region |
E620306
|
entity |
| Predicate | hasLegalCustom |
P3013
|
FINISHED |
| Object | adat (customary law) |
—
|
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: adat (customary law) | Statement: [Madura cultural region, hasLegalCustom, adat (customary law)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalCustom Context triple: [Madura cultural region, hasLegalCustom, adat (customary law)]
-
A.
hasLegalCodeCharacteristic
Indicates that a legal code possesses a specified characteristic, feature, or property.
-
B.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
-
C.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
D.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
E.
usesLegalCode
chosen
Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:47 a.m.