Triple
T19594918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sampati |
E470326
|
entity |
| Predicate | mythologicalLineage |
P75323
|
FINISHED |
| Object | descendant of Kashyapa |
—
|
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: descendant of Kashyapa | Statement: [Sampati, mythologicalLineage, descendant of Kashyapa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythologicalLineage Context triple: [Sampati, mythologicalLineage, descendant of Kashyapa]
-
A.
mythologicalFamily
Indicates a familial relationship between entities within a mythological or legendary context.
-
B.
hasMythologicalFamily
chosen
Indicates that an entity is related to another entity as part of its mythological family or lineage (e.g., gods, heroes, or legendary ancestors).
-
C.
mythologicalGeneration
Indicates a generational relationship in mythology, where one mythological being or group descends from or follows another in a lineage or succession.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640793cd88190b9b84491bfb2493f |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.