Triple
T17981886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Kuru |
E449619
|
entity |
| Predicate | governedByLawCode |
P12605
|
FINISHED |
| Object | Kshatriya dharma |
—
|
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: Kshatriya dharma | Statement: [House of Kuru, governedByLawCode, Kshatriya dharma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByLawCode Context triple: [House of Kuru, governedByLawCode, Kshatriya dharma]
-
A.
governsBodyOfLaw
Indicates that one entity has authoritative control over the creation, interpretation, or enforcement of a particular body of law.
-
B.
governedByAct
Indicates that something is regulated, controlled, or legally defined by a specific act or piece of legislation.
-
C.
governedByLegalRegime
chosen
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
D.
governedInPartBy
Indicates that something is subject to the authority, control, or influence of a governing entity, but only to a limited or partial extent rather than fully.
-
E.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b20431588190a5fe2148a61de403 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.