Triple
T29891854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M. S. Viswanathan |
E759171
|
entity |
| Predicate | groupOrDuoName |
P170748
|
FINISHED |
| Object | Viswanathan–Ramamoorthy |
—
|
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: Viswanathan–Ramamoorthy | Statement: [M. S. Viswanathan, groupOrDuoName, Viswanathan–Ramamoorthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupOrDuoName Context triple: [M. S. Viswanathan, groupOrDuoName, Viswanathan–Ramamoorthy]
-
A.
groupNickname
Indicates that an entity is known by a particular informal or colloquial name used for a group.
-
B.
commonNameGroup
Indicates that multiple entities share the same commonly used name or are grouped under a single common name.
-
C.
supergroupName
Indicates that one entity is the name of a larger group or category (a supergroup) to which another entity belongs.
-
D.
groupOrCluster
Indicates that multiple entities are gathered together or associated as a single group or cluster based on some shared relation or proximity.
-
E.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 6:02 p.m.