Triple
T1268474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nisshoki |
E15655
|
entity |
| Predicate | currentDesignLegallyEstablished |
P4988
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Nisshoki, currentDesignLegallyEstablished, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDesignLegallyEstablished Context triple: [Nisshoki, currentDesignLegallyEstablished, 1999]
-
A.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
currentDesignInForceSince
chosen
Indicates the date or point in time from which the current design has been officially in effect or valid.
-
C.
legalEmbodimentOf
Indicates that one entity serves as the legally recognized form, vehicle, or representation through which another entity exists, acts, or holds rights and obligations in law.
-
D.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
E.
hasLegalInstrument
Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0396e048190b4e2d7aab19268b3 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.