Triple
T19102968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yadava dynasty (by marriage) |
E467580
|
entity |
| Predicate | associatedFigure |
P1183
|
FINISHED |
| Object | Rohini |
—
|
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: Rohini | Statement: [Yadava dynasty (by marriage), associatedFigure, Rohini]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rohini Context triple: [Yadava dynasty (by marriage), associatedFigure, Rohini]
-
A.
Rohini
chosen
Rohini is a prominent figure in Hindu mythology, known as one of Vasudeva’s principal wives and the mother of the hero Balarama.
-
B.
Rohini East
Rohini East is a metro station in Delhi, India, serving the Rohini area as part of the city's rapid transit network.
-
C.
Rohini West
Rohini West is a metro station in the Rohini area of Delhi, India, serving passengers on the Delhi Metro network.
-
D.
Indira Nagar
Indira Nagar is a legislative assembly constituency in the Union Territory of Puducherry, India.
-
E.
Indira Nagar
Indira Nagar is a residential and commercial neighborhood in Chennai, India, known for its urban amenities and proximity to the Adyar area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36e9bfc8190bbaccab169394d99 |
completed | April 20, 2026, 8:27 a.m. |
Created at: April 10, 2026, 12:04 p.m.