Triple
T10814702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 直美 |
E255194
|
entity |
| Predicate | canAlsoBeWrittenIn |
P48646
|
FINISHED |
| Object | hiragana |
—
|
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: hiragana | Statement: [直美, canAlsoBeWrittenIn, hiragana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAlsoBeWrittenIn Context triple: [直美, canAlsoBeWrittenIn, hiragana]
-
A.
canBeWrittenIn
Indicates that something is capable of being expressed, encoded, or represented using a particular language, notation, or medium.
-
B.
isWrittenWith
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
C.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
D.
alsoWrittenAs
Indicates that one entity has an alternative written form, spelling, or notation represented by the other entity.
-
E.
alsoWrittenIn
chosen
Indicates that the same content, work, or information is expressed or available in an additional language, script, or writing system.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733ece4488190b553a66c4b5188bc |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.