Triple
T10576940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kshatriya |
E249634
|
entity |
| Predicate | hasTraditionalDuty |
P76671
|
FINISHED |
| Object | kingship |
—
|
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: kingship | Statement: [Kshatriya, hasTraditionalDuty, kingship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalDuty Context triple: [Kshatriya, hasTraditionalDuty, kingship]
-
A.
traditionalDuty
chosen
Indicates that an entity has an obligation or responsibility toward another entity or activity based on established customs, norms, or longstanding traditions.
-
B.
hasConstitutionalDuty
Indicates that an entity is obligated by a constitution to perform, uphold, or refrain from certain actions or responsibilities.
-
C.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
D.
hasDutyStatus
Indicates that an entity currently holds a particular duty or operational status in relation to a role, task, or assignment.
-
E.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5275628988190bd00dd3f8d7c3937 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.