Triple
T27395860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pnar people |
E691682
|
entity |
| Predicate | customaryLawScope |
P9797
|
FINISHED |
| Object | marriage |
—
|
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: marriage | Statement: [Pnar people, customaryLawScope, marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customaryLawScope Context triple: [Pnar people, customaryLawScope, marriage]
-
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.
civilLawBasedOn
Indicates that a civil law, legal system, or legal provision is derived from, grounded in, or significantly influenced by another specified source of law or legal framework.
-
C.
legalScope
Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
-
D.
haveCivilLaw
Indicates that an entity is subject to, governed by, or operates under a civil law legal system.
-
E.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 12:27 p.m.