Triple
T22888543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Modern Japanese |
E567670
|
entity |
| Predicate | hasStageIn |
P150135
|
FINISHED |
| Object | history of the Japanese language |
—
|
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: history of the Japanese language | Statement: [Early Modern Japanese, hasStageIn, history of the Japanese language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageIn Context triple: [Early Modern Japanese, hasStageIn, history of the Japanese language]
-
A.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
B.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
C.
stagedIn
Indicates that an event, performance, or production takes place or is set within a particular location or venue.
-
D.
hasStageStructure
Indicates that one entity possesses or is characterized by a particular stage-based structural organization defined by another entity.
-
E.
hasStageStart
Indicates that a process, event, or workflow begins or enters a particular stage at a specified point or condition.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:40 p.m.