Triple
T11673828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakya |
E277441
|
entity |
| Predicate | modernDescendantsClaim |
P10101
|
FINISHED |
| Object | Shakya communities in Nepal |
—
|
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: Shakya communities in Nepal | Statement: [Shakya, modernDescendantsClaim, Shakya communities in Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernDescendantsClaim Context triple: [Shakya, modernDescendantsClaim, Shakya communities in Nepal]
-
A.
claimedDescentFrom
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
B.
modernDescendantCommunities
chosen
Indicates that certain present-day communities are descended from, or culturally/lineally continue, earlier groups or populations.
-
C.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
D.
dynasticClaimBasis
Indicates the basis or grounds on which a person or lineage asserts a dynastic right or claim to rule.
-
E.
possibleDescendant
Indicates that one entity may be a descendant of another, without asserting that the descendant relationship is certain.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.