Triple
T11286540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomigusuku |
E267202
|
entity |
| Predicate | hasLocalBelief |
P83048
|
FINISHED |
| Object | Ryukyuan religion |
—
|
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: Ryukyuan religion | Statement: [Tomigusuku, hasLocalBelief, Ryukyuan religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalBelief Context triple: [Tomigusuku, hasLocalBelief, Ryukyuan religion]
-
A.
localBelief
chosen
Indicates that a belief or opinion is held specifically within a particular local context, community, or region rather than being universally accepted.
-
B.
hasVariantBelief
Indicates that one entity holds a belief that is an alternative or differing version of another entity’s belief.
-
C.
hasCentralBelief
Indicates that a particular belief is a core or foundational belief within an entity’s overall belief system.
-
D.
invokesBeliefIn
Indicates that one entity causes, triggers, or calls upon a belief or mental acceptance of something in another entity.
-
E.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e986b0f08190a414749eaa7f1a5d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.