Triple
T10880094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Assembly of the Church of the Nazarene |
E256897
|
entity |
| Predicate | convenesAtInterval |
P46358
|
FINISHED |
| Object | every four years |
—
|
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: every four years | Statement: [General Assembly of the Church of the Nazarene, convenesAtInterval, every four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenesAtInterval Context triple: [General Assembly of the Church of the Nazarene, convenesAtInterval, every four years]
-
A.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
-
B.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
C.
convenesBefore
Indicates that one event or gathering is convened and completed before another specified event or gathering begins.
-
D.
convenesDuring
Indicates that one entity formally gathers or brings together another entity or group during a specified time period or event.
-
E.
intervalAct
chosen
Indicates an action or relationship that occurs over, or is defined by, a specific time interval between 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751af50448190906b47c16878208f |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.