Triple
T27259080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapurush |
E687706
|
entity |
| Predicate | partOfDoubleBillWith |
P59322
|
FINISHED |
| Object | Mahapurush |
—
|
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: Mahapurush | Statement: [Kapurush, partOfDoubleBillWith, Mahapurush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfDoubleBillWith Context triple: [Kapurush, partOfDoubleBillWith, Mahapurush]
-
A.
pairedInDoubleBillWith
chosen
Indicates that two performances, films, or shows are scheduled or presented together as a combined double-feature program.
-
B.
isDoubleAAsideWith
Indicates that two entities are paired together as a double A-side, typically sharing equal prominence in a joint release (such as two lead tracks on the same single).
-
C.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
D.
partOfSingle
Indicates that one entity is a component or member of exactly one specific whole or collection, and not shared among multiple such wholes.
-
E.
isInstallmentOf
Indicates that one entity is an individual installment, part, or episode belonging to a larger, ordered series or whole.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 10:51 a.m.