Triple
T23024436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puran |
E573261
|
entity |
| Predicate | isRelatedToTerm |
P111023
|
FINISHED |
| Object | Purana |
—
|
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: Purana | Statement: [Puran, isRelatedToTerm, Purana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedToTerm Context triple: [Puran, isRelatedToTerm, Purana]
-
A.
relatedToTerm
chosen
Indicates a general, non-specific relationship or association between one term and another.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
hasRelatedTaxon
Indicates a taxonomic relationship between two taxa that are connected in some biologically or taxonomically relevant way, without specifying the exact nature of that relationship.
-
D.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
E.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847b86688190b678d0d09ecd3c3d |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.