Triple
T2656473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Religious Test Clause |
E54622
|
entity |
| Predicate | appliesToOathOrAffirmation |
P3303
|
FINISHED |
| Object | federal officeholders |
—
|
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: federal officeholders | Statement: [No Religious Test Clause, appliesToOathOrAffirmation, federal officeholders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToOathOrAffirmation Context triple: [No Religious Test Clause, appliesToOathOrAffirmation, federal officeholders]
-
A.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
mayBeAffirmedRatherThanSworn
chosen
Indicates that a statement or testimony can be confirmed by affirmation instead of being given under a formal oath.
-
D.
containsOathBy
Indicates that one entity (such as a text, document, or statement) includes or features an oath made by another entity.
-
E.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.