Triple
T19154609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 上川岛 |
E468898
|
entity |
| Predicate | 宗教与信仰特色 |
P33575
|
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.
religiousCharacteristic
chosen
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
-
B.
religiousSceneSpecialization
Indicates a relationship where a scene is specifically characterized or classified by a particular religious theme, context, or function.
-
C.
religiousCulturalContext
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
exploresReligion
Indicates that an entity actively investigates, studies, or seeks to understand a religion or religious belief system.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb81bf08190b0352137eb4a5763 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.