Triple
T6920020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormus Cama |
E160157
|
entity |
| Predicate | characterArcInvolves |
P36856
|
FINISHED |
| Object | rise to global fame |
—
|
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: rise to global fame | Statement: [Ormus Cama, characterArcInvolves, rise to global fame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterArcInvolves Context triple: [Ormus Cama, characterArcInvolves, rise to global fame]
-
A.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
B.
characterArcElement
chosen
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
C.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
D.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
E.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fa452c8190b2bea2d47309c889 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.