Triple
T36892365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakewood Church |
E911780
|
entity |
| Predicate | weeklyAttendance |
P116638
|
FINISHED |
| Object | tens of thousands |
—
|
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: tens of thousands | Statement: [Lakewood Church, weeklyAttendance, tens of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weeklyAttendance Context triple: [Lakewood Church, weeklyAttendance, tens of thousands]
-
A.
homeAttendanceRecord
Indicates that an entity’s record or log of attendance is specifically associated with events or activities held at its home venue or location.
-
B.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
workweekAssociation
Indicates an association between entities based on their connection to a specific workweek or workweek schedule.
-
D.
attendanceUnit
chosen
Indicates a unit or measure used to quantify or record attendance in a given context.
-
E.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd8b718c819094ee0c1fbe434bae |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.