Triple
T30383062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nekomonogatari Black |
E772878
|
entity |
| Predicate | featuresOddity |
P169409
|
FINISHED |
| Object | sawarineko |
—
|
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: sawarineko | Statement: [Nekomonogatari Black, featuresOddity, sawarineko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOddity Context triple: [Nekomonogatari Black, featuresOddity, sawarineko]
-
A.
oddityType
chosen
Indicates the specific category or kind of peculiarity, anomaly, or unusual feature associated with something.
-
B.
specialFeatures
Indicates the distinctive or additional characteristics, functionalities, or attributes that set an entity apart from standard or typical versions.
-
C.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
D.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
E.
featuresStar
Indicates that one entity prominently includes or showcases another entity as a main star or featured performer.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: April 29, 2026, 8:01 p.m.