Triple
T30947309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōtomo clan |
E788431
|
entity |
| Predicate | nameTranscription |
P28703
|
FINISHED |
| Object | Ōtomo |
—
|
NE NERFINISHED |
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: Ōtomo | Statement: [Ōtomo clan, nameTranscription, Ōtomo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameTranscription Context triple: [Ōtomo clan, nameTranscription, Ōtomo]
-
A.
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.
-
B.
transliterationName
Indicates that one entity is the transliterated form of another entity’s name from one writing system into another.
-
C.
nameInLanguageRomanization
Indicates that an entity’s name is represented in the romanized (Latin-script) form of a particular language.
-
D.
nameWrittenIn
Indicates that an entity’s name is written or recorded using a specified language, script, or writing system.
-
E.
alsoTranscribes
Indicates that an entity, in addition to its primary transcription role, transcribes another specified entity as well.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.