Triple
T17518630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minmatar Republic |
E426627
|
entity |
| Predicate | originStoryElement |
P86619
|
FINISHED |
| Object | rebellion against Amarr slavery |
—
|
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: rebellion against Amarr slavery | Statement: [Minmatar Republic, originStoryElement, rebellion against Amarr slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originStoryElement Context triple: [Minmatar Republic, originStoryElement, rebellion against Amarr slavery]
-
A.
originStoryIncludes
chosen
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
B.
originStorySummary
Indicates a brief narrative explaining how something began, was created, or came into existence.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
E.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d0daa48190be69aff32b0324bc |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.