Triple
T35250265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran Empire |
E1018074
|
entity |
| Predicate | successorOrRelatedEntity |
P201639
|
FINISHED |
| Object | Terran Rebellion |
—
|
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: Terran Rebellion | Statement: [Terran Empire, successorOrRelatedEntity, Terran Rebellion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOrRelatedEntity Context triple: [Terran Empire, successorOrRelatedEntity, Terran Rebellion]
-
A.
successorPossiblyRelatedAs
Indicates that one entity is a successor to another in a way that suggests, but does not guarantee, some form of relatedness or continuity between them.
-
B.
successorRelations
Indicates that one entity directly follows or succeeds another in an ordered sequence or progression.
-
C.
successionRelation
Indicates that one entity follows another in an ordered sequence, such as in time, position, or rank.
-
D.
successorOrRelatedProduct
Indicates that one product is a successor to, replacement for, or closely related evolution of another product.
-
E.
successorRelationship
Indicates a relationship where one entity directly follows or replaces another in a sequence, order, or role.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
| PDg | Predicate description generation | batch_6a000fd9602481909ffdc409ac9ca4bb |
completed | May 10, 2026, 4:55 a.m. |
Created at: May 3, 2026, 4:02 p.m.