Triple
T35482235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Six Kingdoms |
E1025497
|
entity |
| Predicate | symbolicChangeTo |
P183789
|
FINISHED |
| Object | rule by chosen monarch |
—
|
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: rule by chosen monarch | Statement: [King of the Six Kingdoms, symbolicChangeTo, rule by chosen monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicChangeTo Context triple: [King of the Six Kingdoms, symbolicChangeTo, rule by chosen monarch]
-
A.
symmetryChange
Indicates a change in the symmetry properties of an entity or system, such as gaining, losing, or altering its symmetry.
-
B.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
mayChangeTo
Indicates that one state, condition, or value is allowed or able to transition into another.
-
D.
reversedChangeOf
Indicates that one entity represents the inverse or opposite direction of a change or transformation described by another entity.
-
E.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 3, 2026, 4:04 p.m.