Triple
T17957548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virata |
E448991
|
entity |
| Predicate | kingdomAttackedBy |
P21625
|
FINISHED |
| Object | Kaurava forces |
—
|
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: Kaurava forces | Statement: [Virata, kingdomAttackedBy, Kaurava forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingdomAttackedBy Context triple: [Virata, kingdomAttackedBy, Kaurava forces]
-
A.
wasInvadedBy
chosen
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
B.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
C.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
-
D.
hasConqueringKing
Indicates that an entity has a king who has conquered or taken control over it or its territory.
-
E.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afb0afe08190964e771ec632fa1e |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.