Triple
T30228917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Constitution |
E768569
|
entity |
| Predicate | consequenceOfAbuse |
P176334
|
FINISHED |
| Object | transition from Galactic Republic to Galactic Empire |
—
|
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: transition from Galactic Republic to Galactic Empire | Statement: [Galactic Constitution, consequenceOfAbuse, transition from Galactic Republic to Galactic Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfAbuse Context triple: [Galactic Constitution, consequenceOfAbuse, transition from Galactic Republic to Galactic Empire]
-
A.
abuse
Indicates that one entity mistreats, harms, or exploits another entity, often in a repeated or severe manner.
-
B.
consequenceOfInjury
Indicates that one event, condition, or outcome occurs as a direct result of a specified injury.
-
C.
typeOfAbuse
Indicates the specific kind or category of abusive behavior that one entity inflicts on another.
-
D.
emotionallyAbuses
Indicates that one entity subjects another to harmful, manipulative, or degrading emotional treatment.
-
E.
periodOfAbuse
Indicates the time span during which abusive behavior occurred or was experienced.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 29, 2026, 7:36 p.m.