Triple
T29043930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin |
E738078
|
entity |
| Predicate | orthographicVariation |
P33995
|
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: [Shin, orthographicVariation, しん]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orthographicVariation Context triple: [Shin, orthographicVariation, しん]
-
A.
orthographicVariant
chosen
Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
-
B.
orthographicIndependence
Indicates that one writing system or orthographic form functions independently of, and is not derived from or constrained by, another.
-
C.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
D.
orthographicPattern
Indicates a relationship where entities share or follow a specific arrangement of written symbols, such as spelling or letter patterns.
-
E.
orthographicProperty
Indicates a relationship where a specific written or spelling-related characteristic is attributed to or associated with an 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6605fcf7c8190b387ad7b65c9f025 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:03 a.m.