Triple
T36217137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udayaditya |
E1047728
|
entity |
| Predicate | stabilized |
P12760
|
FINISHED |
| Object | Paramara kingdom |
—
|
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: Paramara kingdom | Statement: [Udayaditya, stabilized, Paramara kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stabilized Context triple: [Udayaditya, stabilized, Paramara kingdom]
-
A.
stabilizedBy
chosen
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
B.
stabilizationOutcome
Indicates the result or state achieved after a stabilization process has been applied to something.
-
C.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
D.
formedStable
Indicates that a relationship, structure, or configuration has come into existence and remains consistently intact or unchanged over time.
-
E.
stabilizationWork
Indicates actions taken to reinforce, secure, or steady something to prevent deterioration, failure, or unwanted change.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b57e4d788190b8dbcb178a0fe285 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.