Triple
T20991258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noetianism |
E517027
|
entity |
| Predicate | churchResponse |
P142389
|
FINISHED |
| Object | disciplinary action against Noetus and his followers |
—
|
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: disciplinary action against Noetus and his followers | Statement: [Noetianism, churchResponse, disciplinary action against Noetus and his followers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchResponse Context triple: [Noetianism, churchResponse, disciplinary action against Noetus and his followers]
-
A.
churchFunction
Indicates the role, purpose, or function that a church serves in relation to its activities, community, or religious practices.
-
B.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
C.
withinChurch
Indicates that one entity is located inside or contained within a church.
-
D.
addressesChurch
Indicates that one entity delivers a speech, message, or communication specifically directed to a church or church congregation.
-
E.
churchCommunion
Indicates a relationship in which an individual or group participates in or is in fellowship with a particular church community or denomination.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1ba3d0819080d9d03817a45026 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:50 p.m.