Triple
T2472611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon 28 |
E55011
|
entity |
| Predicate | changedHierarchy |
P12792
|
FINISHED |
| Object | placed Constantinople immediately after Rome in honor |
—
|
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: placed Constantinople immediately after Rome in honor | Statement: [Canon 28, changedHierarchy, placed Constantinople immediately after Rome in honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedHierarchy Context triple: [Canon 28, changedHierarchy, placed Constantinople immediately after Rome in honor]
-
A.
hadRankStructureReformedIn
chosen
Indicates that an entity’s rank structure was reorganized, modified, or reformed during a specified time or in a specified context.
-
B.
alignmentChange
Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
E.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.