Triple
T8752958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hepburn romanization |
E208003
|
entity |
| Predicate | primaryScriptTranscribed |
P6524
|
FINISHED |
| Object | Japanese kana |
—
|
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: Japanese kana | Statement: [Hepburn romanization, primaryScriptTranscribed, Japanese kana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScriptTranscribed Context triple: [Hepburn romanization, primaryScriptTranscribed, Japanese kana]
-
A.
transcription
Indicates the process by which genetic information in DNA is copied into RNA by RNA polymerase.
-
B.
primaryScript
chosen
Indicates the writing system or script that is chiefly used to represent the language or content of an entity.
-
C.
transcribedAs
Indicates that one entity is a written or recorded representation of another entity’s content, typically converting it from one form (e.g., audio, handwriting) into text.
-
D.
scripted
Indicates that one entity has written or created the script or dialogue for another entity or event.
-
E.
formerScript
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da8cc548190a31ad542d2faf2d5 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.