Triple
T25699309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pankaj Roy |
E644411
|
entity |
| Predicate | recordPartner |
P133372
|
FINISHED |
| Object | Vinoo Mankad |
—
|
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: Vinoo Mankad | Statement: [Pankaj Roy, recordPartner, Vinoo Mankad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordPartner Context triple: [Pankaj Roy, recordPartner, Vinoo Mankad]
-
A.
partnershipRecord
chosen
Indicates a documented formal partnership relationship established between two or more entities.
-
B.
recordAuthority
Indicates that an entity serves as the authoritative source or controlling body responsible for creating, maintaining, or validating a particular record.
-
C.
recordDriver
Indicates that an entity documents or logs information about a driver, such as their identity, actions, or performance.
-
D.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
E.
recordLabelAssociated
Indicates that one entity (typically an artist or release) is or has been signed to, released under, or otherwise officially affiliated with a particular record label.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 8:42 p.m.