Triple
T25231804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aravidu dynasty |
E632235
|
entity |
| Predicate | ruledRemnantsOf |
P158049
|
FINISHED |
| Object | Vijayanagara Empire |
—
|
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: Vijayanagara Empire | Statement: [Aravidu dynasty, ruledRemnantsOf, Vijayanagara Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledRemnantsOf Context triple: [Aravidu dynasty, ruledRemnantsOf, Vijayanagara Empire]
-
A.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
B.
lastRemnantOf
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
-
C.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
D.
remnantType
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
E.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc8b158819095e054bcde25648f |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:06 p.m.