Triple
T22888555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Modern Japanese |
E567670
|
entity |
| Predicate | spokenVarietiesInclude |
P84576
|
FINISHED |
| Object | Edo dialect |
—
|
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: Edo dialect | Statement: [Early Modern Japanese, spokenVarietiesInclude, Edo dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenVarietiesInclude Context triple: [Early Modern Japanese, spokenVarietiesInclude, Edo dialect]
-
A.
hasLinguisticVariety
chosen
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
B.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
-
C.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
D.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
E.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc37a448190996e106aacc900f4 |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.