Triple
T38697330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Episcopal congregations |
E950037
|
entity |
| Predicate | areOrganizedAs |
P4786
|
FINISHED |
| Object | parishes |
—
|
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: parishes | Statement: [Mississippi Episcopal congregations, areOrganizedAs, parishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areOrganizedAs Context triple: [Mississippi Episcopal congregations, areOrganizedAs, parishes]
-
A.
organizedAs
chosen
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
isOrganized
Indicates that an entity arranges, structures, or systematizes another entity or set of elements according to some order or plan.
-
C.
organizedWith
Indicates that entities are arranged, structured, or coordinated together as part of the same organizing scheme or effort.
-
D.
isOrganizedThrough
Indicates that an activity, event, or process is arranged, coordinated, or carried out by means of a particular intermediary, structure, or channel.
-
E.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.