Triple
T24817044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naidaijin |
E620952
|
entity |
| Predicate | usedInGovernmentSystem |
P23524
|
FINISHED |
| Object | Ritsuryō system |
—
|
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: Ritsuryō system | Statement: [Naidaijin, usedInGovernmentSystem, Ritsuryō system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInGovernmentSystem Context triple: [Naidaijin, usedInGovernmentSystem, Ritsuryō system]
-
A.
usedInGovernmentIn
chosen
Indicates that something is employed, applied, or functions within the context of a specific government or governmental system.
-
B.
usedInGovernmentBody
Indicates that an entity is employed by, serves within, or is otherwise functionally involved in the operations of a government body.
-
C.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
D.
usedAdministrativeSystemOf
Indicates that one entity made use of another entity’s administrative system to perform or manage its administrative functions.
-
E.
governmentUseVariant
Indicates that a government employs or applies an alternative or modified form of something (e.g., a policy, standard, or resource) instead of the primary version.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:03 a.m.