Triple
T30505546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Frum movement |
E776258
|
entity |
| Predicate | hasRitualDay |
P180539
|
FINISHED |
| Object | 15 February |
—
|
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: 15 February | Statement: [John Frum movement, hasRitualDay, 15 February]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualDay Context triple: [John Frum movement, hasRitualDay, 15 February]
-
A.
hasRitualCalendar
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
-
B.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
hasRitualSetting
Indicates that an entity is associated with a specific ritual context or environment in which it is performed, observed, or situated.
-
E.
hasRitualRule
Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.