Triple
T27773239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushyamitras |
E699112
|
entity |
| Predicate | politicalRelationToGuptas |
P150178
|
FINISHED |
| Object | enemy |
—
|
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: enemy | Statement: [Pushyamitras, politicalRelationToGuptas, enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalRelationToGuptas Context triple: [Pushyamitras, politicalRelationToGuptas, enemy]
-
A.
relationshipWithBharata
Indicates that there exists a specific type of relationship or association between an entity and Bharata.
-
B.
governingRelation
Indicates a relationship in which one entity exercises authority, control, or regulatory power over another.
-
C.
relationshipToKauravas
Indicates the type or nature of a person's familial or social relationship to the Kauravas.
-
D.
historicalRelationsWith
chosen
Indicates a relationship where one entity has documented or recognized connections, interactions, or associations with another entity in the past.
-
E.
governingPowerRelationship
Indicates a relationship where one entity holds authoritative control, influence, or ruling power over another entity.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 5:03 p.m.