Triple
T30933333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mindy Lahiri |
E788052
|
entity |
| Predicate | metaReferenceOf |
P170315
|
FINISHED |
| Object | Mindy Kaling |
—
|
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: Mindy Kaling | Statement: [Mindy Lahiri, metaReferenceOf, Mindy Kaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metaReferenceOf Context triple: [Mindy Lahiri, metaReferenceOf, Mindy Kaling]
-
A.
referenceSectionFor
Indicates a relationship where one resource serves as the reference section or reference material specifically associated with another resource.
-
B.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
C.
articleReference
Indicates that one entity cites, mentions, or refers to another entity within an article or written document.
-
D.
crossReference
Indicates that one entity refers the user to another related entity or source for additional or supporting information.
-
E.
hasReferenceWork
Indicates that one entity is associated with a reference work (such as a dictionary, encyclopedia, or manual) that provides authoritative information about it.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e2c1f08190a2f44e4e4575b6cd |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:52 p.m.