Triple
T21939158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loona |
E541769
|
entity |
| Predicate | character |
P662
|
FINISHED |
| Object | Puran |
—
|
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: Puran | Statement: [Loona, character, Puran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Puran Context triple: [Loona, character, Puran]
-
A.
Puran
chosen
Puran is a masculine given name commonly used in South Asia, particularly in India and Nepal.
-
B.
Puran
Puran is a town and administrative subdivision located in Shangla District of Pakistan’s Khyber Pakhtunkhwa province.
-
C.
Purana
The Purana is a genre of ancient Indian literature comprising mythological narratives, cosmology, genealogies, and religious teachings central to Hindu tradition.
-
D.
Purattasi
Purattasi is a significant month in the Tamil calendar, traditionally associated with special religious observances and devotion to Lord Venkateswara.
-
E.
Purochana
Purochana is a character in the Indian epic Mahabharata, known as the architect of the Lakshagriha (lacquer house) built as part of a plot to kill the Pandavas.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241f582c81909a244419cec38b19 |
completed | April 28, 2026, 9:18 p.m. |
Created at: April 16, 2026, 7:55 p.m.