Triple
T10249818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kar |
E240310
|
entity |
| Predicate | chosenAs |
P10044
|
FINISHED |
| Object | successor to the mystical protector |
—
|
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: successor to the mystical protector | Statement: [Kar, chosenAs, successor to the mystical protector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chosenAs Context triple: [Kar, chosenAs, successor to the mystical protector]
-
A.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
B.
selectedTo
chosen
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
C.
madeChoiceBetween
Indicates that an entity selected one option from among two or more specified alternatives.
-
D.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:28 a.m.