Triple
T27004619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 金光教 |
E680207
|
entity |
| Predicate | 重視する実践 |
P1188
|
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.
hasImportantPractice
chosen
Indicates that an entity engages in or possesses a practice, activity, or procedure considered significant or essential within a given context.
-
B.
actualPractice
Indicates that an action, method, or behavior is carried out in reality or in day-to-day use, as opposed to being merely theoretical, planned, or prescribed.
-
C.
publicPractice
Indicates that an activity, behavior, or belief is carried out openly in public or within a community setting rather than privately.
-
D.
supportedPractice
Indicates that one entity endorses, promotes, or facilitates the use of a particular practice by another entity.
-
E.
emblematicPractice
Indicates a practice or behavior that symbolically represents, expresses, or typifies a group, identity, or concept.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d139f081909f9ca04e04095dba |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7 a.m.