Triple
T29299514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini Ganesan |
E742921
|
entity |
| Predicate | coevalWith |
P6401
|
FINISHED |
| Object | M. G. Ramachandran |
—
|
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: M. G. Ramachandran | Statement: [Gemini Ganesan, coevalWith, M. G. Ramachandran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coevalWith Context triple: [Gemini Ganesan, coevalWith, M. G. Ramachandran]
-
A.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
B.
contemporaryWith
chosen
Indicates that two entities existed, occurred, or were active during the same time period.
-
C.
isMostlyConcurrentWith
Indicates that two events or intervals overlap in time for the majority of their durations, though not necessarily starting or ending together.
-
D.
isEquiconsistentWith
Indicates that two formal theories or systems have the same consistency strength, such that if one is consistent then the other is also consistent, and if one is inconsistent then so is the other.
-
E.
coEternalWith
Indicates that two entities have existed for the same infinite duration, without either one preceding the other in time.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a1a7148190ae6060514d16ffec |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:09 p.m.