Triple
T29142441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amethyst, Princess of Gemworld |
E738672
|
entity |
| Predicate | protagonistTrueOrigin |
P28569
|
FINISHED |
| Object | Gemworld |
—
|
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: Gemworld | Statement: [Amethyst, Princess of Gemworld, protagonistTrueOrigin, Gemworld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistTrueOrigin Context triple: [Amethyst, Princess of Gemworld, protagonistTrueOrigin, Gemworld]
-
A.
protagonistOrigin
chosen
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
B.
protagonistOriginTime
Indicates the point in time at which the protagonist first comes into existence or begins their story.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
protagonistBasedOn
Indicates that a fictional work’s main character is modeled on, inspired by, or derived from a particular real or fictional person or entity.
-
E.
protagonistFamilyOrigin
Indicates that a character’s family background, ancestry, or place of origin is associated with the story’s protagonist.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 11:37 a.m.