Triple
T28142170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptist Church in Charleston |
E714372
|
entity |
| Predicate | hasMeetingDay |
P26202
|
FINISHED |
| Object | Sunday |
—
|
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: Sunday | Statement: [Baptist Church in Charleston, hasMeetingDay, Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingDay Context triple: [Baptist Church in Charleston, hasMeetingDay, Sunday]
-
A.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
-
B.
hasMeetingSchedule
Indicates that an entity has an associated plan or timetable specifying when meetings are to occur.
-
C.
hasMeetings
Indicates that an entity participates in or is associated with one or more scheduled meetings.
-
D.
hasPrimaryMeeting
Indicates that an entity is associated with its main or most important meeting, distinguishing it from other meetings it may have.
-
E.
meetingDay
chosen
Indicates the specific day on which a meeting is scheduled or takes place between the related entities.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 9:54 p.m.