Triple
T32317042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kantokuen |
E825666
|
entity |
| Predicate | alternativeDoctrine |
P180171
|
FINISHED |
| Object | Nanshin-ron |
—
|
NE NERFINISHED |
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: Nanshin-ron | Statement: [Kantokuen, alternativeDoctrine, Nanshin-ron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeDoctrine Context triple: [Kantokuen, alternativeDoctrine, Nanshin-ron]
-
A.
currentDoctrine
Indicates the doctrine, policy, or set of guiding principles that is presently in force or officially adopted at a given time.
-
B.
proposesDoctrine
Indicates that one entity formally puts forward or advocates a particular doctrine, theory, or set of principles for consideration or adoption by others.
-
C.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
D.
appliedDoctrine
Indicates that a particular doctrine, principle, or rule has been put into practice or used in interpreting or deciding a specific case, situation, or context.
-
E.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
- F. None of above. chosen
Provenance (4 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: May 1, 2026, 12:46 a.m.