Triple
T30584180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakusandha Buddha |
E778459
|
entity |
| Predicate | birthCountryTraditional |
P37939
|
FINISHED |
| Object | Ancient India |
—
|
NE NERFINISHED |
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: Ancient India | Statement: [Kakusandha Buddha, birthCountryTraditional, Ancient India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthCountryTraditional Context triple: [Kakusandha Buddha, birthCountryTraditional, Ancient India]
-
A.
countryOfNamingTradition
Indicates the country whose cultural or linguistic naming conventions are used to form or interpret a given name.
-
B.
primaryAncestralCountry
Indicates the country that is considered the main place of origin for an individual’s or group’s ancestors.
-
C.
onTraditionalCountryOf
Indicates that something is located within or associated with the traditional country or ancestral lands of a particular group.
-
D.
countryOfHeritage
Indicates the country from which an entity’s cultural, ancestral, or familial heritage originates.
-
E.
nativeCountry
chosen
Indicates the country in which an entity (typically a person) was born or is originally from.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:23 p.m.