Triple
T38242459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kit Young |
E1013800
|
entity |
| Predicate | notableCharacterIs |
P137625
|
FINISHED |
| Object | Grisha universe character |
—
|
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: Grisha universe character | Statement: [Kit Young, notableCharacterIs, Grisha universe character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterIs Context triple: [Kit Young, notableCharacterIs, Grisha universe character]
-
A.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
B.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
C.
notableSeriesCharacter
chosen
Indicates that an entity is a significant or well-known character appearing in a particular series.
-
D.
notableWorkCharacter
Indicates that a character appears in, is associated with, or plays a role in a particular notable work.
-
E.
notableCharacterCreated
Indicates that one entity is a notable or significant character that was created by another entity.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.