Triple
T24288290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sakoku |
E605735
|
entity |
| Predicate | hasKeyEdict |
P6200
|
FINISHED |
| Object | Sakoku edicts of 1633 |
—
|
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: Sakoku edicts of 1633 | Statement: [sakoku, hasKeyEdict, Sakoku edicts of 1633]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyEdict Context triple: [sakoku, hasKeyEdict, Sakoku edicts of 1633]
-
A.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
-
B.
hasKeyAct
Indicates that one entity possesses or is associated with a primary or central action related to another entity.
-
C.
hasKeyDua
Indicates that one entity possesses or is associated with a specific secondary or backup key related to another entity.
-
D.
hasKeyWork
chosen
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
E.
hasKeyThinker
Indicates that an entity is associated with or characterized by a particular key thinker (e.g., philosopher, theorist, or intellectual figure) central to its ideas or development.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f57a9a08190b183879ff76071d0 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.