Triple
T36993815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yōrō era |
E915175
|
entity |
| Predicate | legalCodeImplementation |
P201297
|
FINISHED |
| Object | Yōrō Code enforced in early 8th century |
—
|
NE NERFINISHED |
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 enforced in early 8th century | Statement: [Yōrō era, legalCodeImplementation, Yōrō Code enforced in early 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCodeImplementation Context triple: [Yōrō era, legalCodeImplementation, Yōrō Code enforced in early 8th century]
-
A.
legalCodeScript
Indicates that a legal code is written or represented using a particular writing system or script.
-
B.
legalCodeCompiledBy
Indicates that a legal code or body of laws has been assembled, organized, or formally compiled by a particular agent or authority.
-
C.
legalCodePreceded
Indicates that one legal code existed or was in force before another legal code in a temporal or historical sequence.
-
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.
legalCodeAvailableAt
Indicates that a particular legal code or statute can be accessed, obtained, or consulted at a specified source or location.
- 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_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
| PDg | Predicate description generation | batch_69ffe6e21f748190a18dfe0878d397f7 |
completed | May 10, 2026, 2:01 a.m. |
Created at: May 3, 2026, 4:14 p.m.