Triple
T2871101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presbyterian Church (USA) |
E63561
|
entity |
| Predicate | layOffice |
P43436
|
FINISHED |
| Object | ruling elder |
—
|
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: ruling elder | Statement: [Presbyterian Church (USA), layOffice, ruling elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layOffice Context triple: [Presbyterian Church (USA), layOffice, ruling elder]
-
A.
limitsOffice
Indicates that one entity imposes a restriction or cap on the scope, duration, or powers of another entity’s office or official position.
-
B.
office
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
C.
inOfficeFrom
Indicates that an entity holds a particular office or position starting from a specified date or time.
-
D.
leftOffice
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
E.
defaultOfficeSuite
Indicates that a particular office software suite is set as the primary or standard choice to be used by default.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe2dcb48190a194253e733d14af |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.