Triple
T30933334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mindy Lahiri |
E788052
|
entity |
| Predicate | selfReferentialCounterpartOf |
P94153
|
FINISHED |
| Object | Kelly Kapoor |
—
|
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: Kelly Kapoor | Statement: [Mindy Lahiri, selfReferentialCounterpartOf, Kelly Kapoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfReferentialCounterpartOf Context triple: [Mindy Lahiri, selfReferentialCounterpartOf, Kelly Kapoor]
-
A.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
B.
hasCounterpartName
Indicates that an entity has an alternative or corresponding name used as its counterpart in another context, system, or representation.
-
C.
counterpartRelation
chosen
Indicates a reciprocal relationship where two entities serve as corresponding or equivalent counterparts to each other in a given context.
-
D.
hasSmallerCounterpart
Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
-
E.
hasCounterpartNickname
Indicates that one entity is used as an alternative or counterpart nickname for another entity.
- 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_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. |
Created at: April 29, 2026, 8:52 p.m.