Triple
T27375124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arun Kumar Chatterjee |
E691043
|
entity |
| Predicate | hasScreenName |
P137472
|
FINISHED |
| Object | Uttam Kumar |
—
|
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: Uttam Kumar | Statement: [Arun Kumar Chatterjee, hasScreenName, Uttam Kumar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenName Context triple: [Arun Kumar Chatterjee, hasScreenName, Uttam Kumar]
-
A.
screenName
chosen
Indicates the display or handle name associated with an entity, typically used as its visible identifier in user interfaces or social platforms.
-
B.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
-
C.
hasUsername
Indicates that an entity is associated with a specific username used to identify it within a system or context.
-
D.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
E.
hasNetworkName
Indicates that an entity is associated with a specific network identifier or name.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 12:20 p.m.