Triple
T29056151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Colchis |
E735389
|
entity |
| Predicate | titleHolderSpouseInMyth |
P41899
|
FINISHED |
| Object | Jason |
—
|
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: Jason | Statement: [Princess of Colchis, titleHolderSpouseInMyth, Jason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderSpouseInMyth Context triple: [Princess of Colchis, titleHolderSpouseInMyth, Jason]
-
A.
titleHolderSpouseInstanceOf
Indicates that the spouse of a title holder is an instance of a specified role, status, or class related to that title.
-
B.
titleHolderSpouseHouse
Indicates that the spouse of the current title holder is associated with or belongs to a particular house or family line.
-
C.
currentTitleHolderSpouseOf
chosen
Indicates that one entity is the current spouse of the individual who presently holds a specified title.
-
D.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
E.
titleFromSpouse
Indicates that an entity holds a title or honorific that is derived from or acquired through their spouse.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 10:11 a.m.