Triple
T28705798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anubhav |
E729691
|
entity |
| Predicate | hasSignificantRoleBy |
P169911
|
FINISHED |
| Object | Sanjay Suri |
—
|
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: Sanjay Suri | Statement: [Anubhav, hasSignificantRoleBy, Sanjay Suri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantRoleBy Context triple: [Anubhav, hasSignificantRoleBy, Sanjay Suri]
-
A.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
-
C.
hasGoverningRole
Indicates that one entity holds an official position of authority, control, or governance over another entity or domain.
-
D.
hasPlayingRole
chosen
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
E.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 5:45 a.m.