Triple
T877654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peace through law |
E18957
|
entity |
| Predicate | seeksToReplace |
P21015
|
FINISHED |
| Object | power politics with legal regulation |
—
|
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: power politics with legal regulation | Statement: [Peace through law, seeksToReplace, power politics with legal regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksToReplace Context triple: [Peace through law, seeksToReplace, power politics with legal regulation]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
replacedEntity
Indicates that one entity has been substituted for, or taken the place of, another entity in a given context.
-
C.
replacedStructure
Indicates that one structure has been substituted for, or taken the place of, another structure.
-
D.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
E.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb06ea88190962502172d434eb4 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.