Triple
T15013401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soka Gakkai Men’s Division |
E377894
|
entity |
| Predicate | isLayOrganization |
P116357
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Soka Gakkai Men’s Division, isLayOrganization, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLayOrganization Context triple: [Soka Gakkai Men’s Division, isLayOrganization, true]
-
A.
hasLayOrganizationType
Indicates that an entity is associated with a specific type or category of lay (non-clerical) organizational structure.
-
B.
hasLayOffice
Indicates that an individual holds or has held a non-ordained (lay) official position or role within an organization or institution.
-
C.
hasLayGovernanceBody
Indicates that an organization is overseen or advised by a governance body composed primarily of non-clerical or non-executive lay members.
-
D.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
-
E.
hasFrontOrganization
Indicates that an entity is represented, covered, or operated through another entity that serves as its front or façade organization.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7613cec8190ac25e3f68c5d0edf |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.