Triple
T27872520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial remnant |
E704825
|
entity |
| Predicate | hasCanonStatus |
P115170
|
FINISHED |
| Object | primarily Legends |
—
|
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: primarily Legends | Statement: [Imperial remnant, hasCanonStatus, primarily Legends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonStatus Context triple: [Imperial remnant, hasCanonStatus, primarily Legends]
-
A.
hasCanonization
Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
-
B.
inCanonStatus
chosen
Indicates that an entity’s status is whether it is considered part of the official canon within a given fictional or narrative universe.
-
C.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
D.
hasClosedCanon
Indicates that a body of authoritative texts is considered complete and no additional works can be added to it.
-
E.
canonicalStatusIn
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 6:25 p.m.