Triple
T13721485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rina |
E329046
|
entity |
| Predicate | scriptInJapanese |
P31360
|
FINISHED |
| Object | りな |
—
|
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: りな | Statement: [Rina, scriptInJapanese, りな]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptInJapanese Context triple: [Rina, scriptInJapanese, りな]
-
A.
JapaneseFormation
Indicates a relationship where something is formed, created, or organized according to Japanese style, methods, or origin.
-
B.
japaneseOnReading
Indicates the on-yomi (Sino-Japanese) pronunciation associated with a given Japanese kanji or term.
-
C.
japaneseVariant
Indicates that one entity is a Japanese-language or Japan-specific variant or version of another entity.
-
D.
hasJapaneseText
chosen
Indicates that an entity contains or is associated with text written in the Japanese language.
-
E.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f3b46481909ceedfa78e9ca92b |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.