Triple
T36993814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yōrō era |
E915175
|
entity |
| Predicate | legalCodePromulgation |
P201284
|
FINISHED |
| Object | Yōrō Code promulgated 718 |
—
|
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: Yōrō Code promulgated 718 | Statement: [Yōrō era, legalCodePromulgation, Yōrō Code promulgated 718]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCodePromulgation Context triple: [Yōrō era, legalCodePromulgation, Yōrō Code promulgated 718]
-
A.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
-
B.
lawCollection
Indicates a relationship in which a set of legal rules, statutes, or regulations is grouped or organized together as a collection.
-
C.
legalCodeFamily
Indicates that one legal code belongs to, or is categorized under, a broader family or system of related legal codes.
-
D.
legalCodeName
Indicates that one entity is the official legal code designation or name assigned to another entity within a legal or regulatory system.
-
E.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69ffe6130698819099328fce92bb2784 |
completed | May 10, 2026, 1:57 a.m. |
Created at: May 3, 2026, 4:14 p.m.