Triple
T3616347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 山本 |
E76608
|
entity |
| Predicate | belongsToWritingSystem |
P454
|
FINISHED |
| Object | Japanese writing system |
—
|
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 writing system | Statement: [山本, belongsToWritingSystem, Japanese writing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToWritingSystem Context triple: [山本, belongsToWritingSystem, Japanese writing system]
-
A.
writingSystemClass
Indicates that one entity is classified as a type or category of writing system to which the other entity belongs.
-
B.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
C.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
D.
hasWritingSystemForMajorLanguage
Indicates that there exists a writing system used to represent a major language associated with the given entity.
-
E.
writingSystemFeatures
Indicates the specific structural or functional characteristics that define how a particular writing system represents language.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27c98088190a493c9eddf6b206a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.