Triple
T30344916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | abec |
E771845
|
entity |
| Predicate | hasCreatedCharactersFor |
P176002
|
FINISHED |
| Object | Sword Art Online light novels |
—
|
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: Sword Art Online light novels | Statement: [abec, hasCreatedCharactersFor, Sword Art Online light novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatedCharactersFor Context triple: [abec, hasCreatedCharactersFor, Sword Art Online light novels]
-
A.
hasCreatedCharacterFor
chosen
Indicates that one entity has created or designed a character specifically for another entity or context.
-
B.
coCreatedCharactersWith
Indicates that two or more entities jointly created one or more characters together.
-
C.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
D.
hasHumanCharacters
Indicates that the subject includes or features characters that are human beings.
-
E.
hasFounderCharacter
Indicates that an entity has a founder who possesses a specified character trait or set of personal qualities.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 7:55 p.m.