Triple
T18426733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-American Council of the Orthodox Church in America |
E450158
|
entity |
| Predicate | hasDelegateType |
P16808
|
FINISHED |
| Object | clergy |
—
|
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: clergy | Statement: [All-American Council of the Orthodox Church in America, hasDelegateType, clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDelegateType Context triple: [All-American Council of the Orthodox Church in America, hasDelegateType, clergy]
-
A.
hasActingType
Indicates that an entity participates in or performs an action in a specified manner, role, or mode of acting.
-
B.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasDependenceType
Indicates the specific kind or category of dependence that one entity has on another.
-
D.
hasAssociatedType
Indicates that one entity is linked to another entity that specifies its type, category, or classification.
-
E.
hasTaskType
Indicates that an entity is associated with or classified under a specific type or category of task.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b13ee88819091e7e007d17dcc73 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:24 a.m.