Triple
T38495948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Jessamine Kaldwin |
E919692
|
entity |
| Predicate | positionOfCorvoAttano |
P201903
|
FINISHED |
| Object | Royal Protector |
—
|
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: Royal Protector | Statement: [Empress Jessamine Kaldwin, positionOfCorvoAttano, Royal Protector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfCorvoAttano Context triple: [Empress Jessamine Kaldwin, positionOfCorvoAttano, Royal Protector]
-
A.
antagonistLocationFor
Indicates that a location serves as the primary place where an antagonist operates, resides, or exerts influence in relation to a given context or entity.
-
B.
positionInNavadurga
Indicates the specific role or placement an entity holds within the Navadurga (nine forms of Durga) grouping or sequence.
-
C.
positionInParadiso
Indicates the specific location or rank an entity holds within the structure or hierarchy of Paradiso.
-
D.
positionOfLanzón
Indicates the spatial location or placement of the Lanzón relative to its surrounding context or reference frame.
-
E.
AVALocation
Indicates that an entity’s location is specified or associated with a particular place or spatial position.
- F. None of above. chosen
Provenance (4 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
| PDg | Predicate description generation | batch_6a002f071de88190b1fa4f5531a6cea7 |
completed | May 10, 2026, 7:08 a.m. |
Created at: May 3, 2026, 4:31 p.m.