Triple
T29893895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration of a New Order |
E759224
|
entity |
| Predicate | declaresEndOf |
P168222
|
FINISHED |
| Object | Galactic Republic |
—
|
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: Galactic Republic | Statement: [Declaration of a New Order, declaresEndOf, Galactic Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaresEndOf Context triple: [Declaration of a New Order, declaresEndOf, Galactic Republic]
-
A.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
B.
endOfState
Indicates the point or condition at which a particular state, situation, or process comes to an end.
-
C.
functionEnd
Indicates the point or condition at which a function, process, or operation terminates or completes.
-
D.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
E.
representationEnded
Indicates that a previously ongoing representation or acting-on-behalf-of relationship between entities has come to an end.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67729a7ac8190b99cf3fcc0e2c60c |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:03 p.m.