Triple
T60132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In God We Trust |
E1191
|
entity |
| Predicate | judicialCharacterization |
P662
|
FINISHED |
| Object | ceremonial deism |
—
|
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: ceremonial deism | Statement: [In God We Trust, judicialCharacterization, ceremonial deism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialCharacterization Context triple: [In God We Trust, judicialCharacterization, ceremonial deism]
-
A.
bindingNatureOfJudgments
Indicates that judgments or decisions have a compulsory, legally enforceable effect on the parties or entities to which they apply.
-
B.
judge
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
-
C.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
D.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
judicialCapital
Indicates that a location serves as the primary seat of judicial authority or houses the main courts for a given region or jurisdiction.
- 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_69a24a552ef88190a0df287d68c65cba |
completed | Feb. 28, 2026, 1:52 a.m. |
| NER | Named-entity recognition | batch_69a251a1b8ac8190b44be4c3c41e5681 |
completed | Feb. 28, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69a24ea0bec48190b2af1fb287e9e692 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 1:55 a.m.