Triple
T31279577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kōji |
E797622
|
entity |
| Predicate | hasThirdMora |
P12765
|
FINISHED |
| Object | じ (ji) |
—
|
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: じ (ji) | Statement: [Kōji, hasThirdMora, じ (ji)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThirdMora Context triple: [Kōji, hasThirdMora, じ (ji)]
-
A.
thirdSyllable
Indicates that one entity is the third syllable within, or corresponding to, another entity (such as a word or phrase).
-
B.
hasThirdVarna
Indicates that an entity belongs to, or is associated with, the third varna (social class) in a varna-based classification system.
-
C.
hasThirdLetter
chosen
Indicates that a string or sequence possesses a specific character or element in the third position.
-
D.
hasNasalHarmony
Indicates that a phonological process causes nasality in one segment to spread to or be shared with other segments within a word or domain.
-
E.
hasFinalSyllable
Indicates that one entity possesses or ends with a specific final syllable represented by the other 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 9:13 p.m.