Triple
T15650289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amane |
E376292
|
entity |
| Predicate | isTranscribedAs |
P28703
|
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: [Amane, isTranscribedAs, あまね]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTranscribedAs Context triple: [Amane, isTranscribedAs, あまね]
-
A.
isTranscriptionOf
Indicates that one entity is a written, typed, or otherwise recorded representation of the content of another entity, preserving its original form as closely as possible.
-
B.
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.
-
C.
alsoTranscribes
Indicates that an entity, in addition to its primary transcription role, transcribes another specified entity as well.
-
D.
transcription
Indicates the process by which genetic information in DNA is copied into RNA by RNA polymerase.
-
E.
transcribedName
chosen
Indicates that one entity is a written or phonetic rendering of another entity’s name, typically adapted to a different script, language, or transcription 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eeed2d48190a7a8a618d90012d0 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.