Triple
T23497464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese law |
E571739
|
entity |
| Predicate | modernFormBegan |
P8393
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Japanese law, modernFormBegan, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernFormBegan Context triple: [Japanese law, modernFormBegan, late 19th century]
-
A.
modernFormSince
chosen
Indicates that an entity has existed in its current or modern form starting from a specified point in time.
-
B.
standardModernForm
Indicates that an entity is expressed or represented in the currently accepted standard modern form of a language, notation, or system.
-
C.
modernPhaseBegins
Indicates that a transition occurs marking the start of a modern phase or period in a process, development, or timeline.
-
D.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
E.
modernProofBy
Indicates that something is established or demonstrated using a contemporary or currently accepted method of proof by a specified agent or process.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e0c5a48190badb8303f40f6180 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.