Triple
T3081436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Socialist Party |
E64264
|
entity |
| Predicate | countryGovernmentLevel |
P1085
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [Japan Socialist Party, countryGovernmentLevel, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryGovernmentLevel Context triple: [Japan Socialist Party, countryGovernmentLevel, national]
-
A.
levelOfGovernment
chosen
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
-
B.
countryGovernment
Indicates the type or form of government that exercises authority over a given country.
-
C.
controlsLevelOfGovernment
Indicates that one entity has authority or power to direct, regulate, or determine the functioning or decisions of a specified level of government.
-
D.
governingBodyLevel
Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
-
E.
governmentalUnit
Indicates that one entity functions as a governmental or administrative unit in relation to another entity.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1aaf6d48190af4f9106965589b0 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.