Triple
T35261082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metamorphosis |
E1018370
|
entity |
| Predicate | franchiseCanonicalStatus |
P168783
|
FINISHED |
| Object | prime canon |
—
|
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: prime canon | Statement: [Metamorphosis, franchiseCanonicalStatus, prime canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseCanonicalStatus Context triple: [Metamorphosis, franchiseCanonicalStatus, prime canon]
-
A.
franchiseStatus
Indicates the current standing or condition of a franchise relationship between parties, such as whether it is active, inactive, pending, or terminated.
-
B.
franchiseCanonStatus
chosen
Indicates whether a work, event, or element is officially recognized as part of the established canon within a franchise.
-
C.
isSuccessfulFranchise
Indicates that a franchise has achieved notable success, typically in terms of popularity, profitability, or sustained growth.
-
D.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
E.
franchiseStatusAfterFolding
Indicates the status or condition of a franchise after it has ceased operations or been folded.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.