Triple
T502551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom Hall |
E10429
|
entity |
| Predicate | meetingSchedule |
P13127
|
FINISHED |
| Object | weekly congregation meetings |
—
|
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: weekly congregation meetings | Statement: [Kingdom Hall, meetingSchedule, weekly congregation meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingSchedule Context triple: [Kingdom Hall, meetingSchedule, weekly congregation meetings]
-
A.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
C.
hasMeeting
chosen
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
-
D.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
E.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.