Triple
T35169081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongo |
E1015491
|
entity |
| Predicate | hasPrimaryWritingSystem |
P139400
|
FINISHED |
| Object | Japanese kanji |
—
|
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 kanji | Statement: [Hongo, hasPrimaryWritingSystem, Japanese kanji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWritingSystem Context triple: [Hongo, hasPrimaryWritingSystem, Japanese kanji]
-
A.
hasTypicalWritingSystem
Indicates that an entity customarily uses a particular writing system as its standard or most common form of written representation.
-
B.
hasWritingSystemForMajorLanguage
Indicates that there exists a writing system used to represent a major language associated with the given entity.
-
C.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
-
D.
hasWritingSystemName
Indicates that a writing system is associated with a particular name or designation.
-
E.
hasOriginalWritingSystem
chosen
Indicates that an entity possesses or is associated with a primary, native, or first-developed writing system used to represent its language or content.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.