Triple
T19595076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaikesi |
E470329
|
entity |
| Predicate | offspringAlignment |
P136412
|
FINISHED |
| Object | Ravana’s lineage |
—
|
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: Ravana’s lineage | Statement: [Kaikesi, offspringAlignment, Ravana’s lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offspringAlignment Context triple: [Kaikesi, offspringAlignment, Ravana’s lineage]
-
A.
offspringWith
Indicates that two entities share a parent–child relationship, specifying that one is the offspring of the other.
-
B.
successorAlignment
Indicates that one entity’s alignment, orientation, or configuration directly follows and is determined by that of another entity in a sequence or progression.
-
C.
offspringGroup
Indicates that one entity is a group or collection composed of the offspring of another entity.
-
D.
offspringType
Indicates the specific kind or category of offspring that results from a parent or reproductive event.
-
E.
basedOnAlignmentOf
Indicates a relationship where one entity is determined, derived, or decided according to how closely it aligns with another entity’s position, orientation, or criteria.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.