Triple
T29558456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asal |
E749969
|
entity |
| Predicate | hasLeadCharacterName |
P186374
|
FINISHED |
| Object | Jeevan |
—
|
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: Jeevan | Statement: [Asal, hasLeadCharacterName, Jeevan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadCharacterName Context triple: [Asal, hasLeadCharacterName, Jeevan]
-
A.
hasCharacterNamedAfter
Indicates that one entity has a character whose name is derived from or intentionally based on another entity.
-
B.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
C.
leadCharacterBasedOn
Indicates that a lead character is derived from, inspired by, or adapted from a particular source entity (such as a real person, another character, or existing work).
-
D.
filmLeadCharacter
Indicates that a person or character serves as the primary or central protagonist in a film.
-
E.
leadCharacterField
Indicates that one entity serves as the primary or main character associated with another entity, such as a work or production.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 28, 2026, 5:18 p.m.