Triple
T15876047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khosrow and Shirin |
E384955
|
entity |
| Predicate | heroineOrigin |
P34184
|
FINISHED |
| Object | Armenian princess |
—
|
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: Armenian princess | Statement: [Khosrow and Shirin, heroineOrigin, Armenian princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroineOrigin Context triple: [Khosrow and Shirin, heroineOrigin, Armenian princess]
-
A.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
B.
originOfCharacter
Indicates the source or place from which a character originates or is created.
-
C.
characterOrigin
chosen
Indicates the source, background, or initial context from which a character originates.
-
D.
notableFemaleHero
Indicates that the subject is a female individual recognized for heroic actions or qualities that make her notably distinguished.
-
E.
antagonistOrigin
Indicates the source, background, or cause from which an antagonist or opposing force arises in relation to another entity 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.