Triple
T36890411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tailapa-deva |
E911730
|
entity |
| Predicate | politicalStatusBeforeRevolt |
P63481
|
FINISHED |
| Object | Rashtrakuta feudatory |
—
|
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: Rashtrakuta feudatory | Statement: [Tailapa-deva, politicalStatusBeforeRevolt, Rashtrakuta feudatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusBeforeRevolt Context triple: [Tailapa-deva, politicalStatusBeforeRevolt, Rashtrakuta feudatory]
-
A.
politicalStatusBeforeReign
Indicates the political role or status an individual held prior to beginning their reign or period of rule.
-
B.
politicalStatusBefore
chosen
Indicates the political status or condition an entity held prior to a specified event, change, or reference point.
-
C.
preRevolutionStatus
Indicates the status or condition of an entity as it existed prior to a specified revolution or revolutionary event.
-
D.
militaryRankBeforeRevolt
Indicates the military rank an individual held prior to participating in or initiating a revolt.
-
E.
preRevolutionOccupation
Indicates the occupation or role a person held before a specific revolution or revolutionary event.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 3, 2026, 4:13 p.m.