Triple
T22851709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 和人 |
E566370
|
entity |
| Predicate | 関連する古代政権 |
P74682
|
FINISHED |
| Object | 大和政権 |
—
|
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: 大和政権 | Statement: [和人, 関連する古代政権, 大和政権]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連する古代政権 Context triple: [和人, 関連する古代政権, 大和政権]
-
A.
associatedWithDynastyPolitics
chosen
Indicates a relationship where an entity is involved in, influenced by, or connected to the political activities, power structures, or governance associated with a particular dynasty.
-
B.
governedPolityThroughDynasty
Indicates that a person or group exercised governing authority over a polity specifically by means of holding power within a particular dynasty.
-
C.
historicalRegime
Indicates that one entity functioned as a governing regime or ruling authority over another entity during a specific historical period.
-
D.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
E.
countryGovernmentSystemDuringExistence
Indicates the form of government a country had during its period of existence.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb9a5b8819091cbb4ac42fbf778 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.