Triple
T4936428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishvamitra |
E110821
|
entity |
| Predicate | laterRelationWith |
P60493
|
FINISHED |
| Object | Vashistha as reconciled peer |
—
|
LITERAL FINISHED |
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: Vashistha as reconciled peer | Statement: [Vishvamitra, laterRelationWith, Vashistha as reconciled peer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRelationWith Context triple: [Vishvamitra, laterRelationWith, Vashistha as reconciled peer]
-
A.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
B.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
D.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
-
E.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7085b1dc819099408f6503f0210f |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:30 p.m.