Triple
T7593073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hepburn |
E179787
|
entity |
| Predicate | transcribes |
P71900
|
FINISHED |
| Object | Japanese syllables |
—
|
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 syllables | Statement: [Hepburn, transcribes, Japanese syllables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transcribes Context triple: [Hepburn, transcribes, Japanese syllables]
-
A.
transcription
Indicates the process by which genetic information in DNA is copied into RNA by RNA polymerase.
-
B.
transcribesPhonologyOf
chosen
Indicates that one entity converts or represents the phonological aspects of another entity into a written, symbolic, or otherwise encoded form.
-
C.
transcriptAvailable
Indicates that a transcript of the referenced content is available for access or use.
-
D.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
E.
translator
Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b92c348190b547f0aacfb8d6be |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.