Triple
T18911789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Elders |
E462626
|
entity |
| Predicate | usesLegalTradition |
P17298
|
FINISHED |
| Object | 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: customary law | Statement: [House of Elders, usesLegalTradition, customary law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLegalTradition Context triple: [House of Elders, usesLegalTradition, customary law]
-
A.
hasLawTradition
chosen
Indicates that one legal system, jurisdiction, or entity follows or is based on a particular legal tradition or family of law.
-
B.
coexistingLegalTradition
Indicates that multiple legal traditions or systems exist and operate simultaneously within the same social or institutional context.
-
C.
legalTraditionInfluenced
Indicates that one legal tradition has had a formative or shaping influence on the development, principles, or practices of another legal tradition.
-
D.
legalTraditionsTaught
Indicates that one entity teaches, covers, or includes specific legal traditions in its instruction or curriculum.
-
E.
usedLegalSystemOf
Indicates that one entity applied, followed, or operated under the legal system or body of laws belonging to 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c6238e288190b30311b5d80beafb |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.