Triple
T32035335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah |
E818079
|
entity |
| Predicate | religiousAppearance |
P33575
|
FINISHED |
| Object | Catholic priest |
—
|
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: Catholic priest | Statement: [Noah, religiousAppearance, Catholic priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAppearance Context triple: [Noah, religiousAppearance, Catholic priest]
-
A.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
B.
religiousCharacteristic
chosen
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
-
C.
religionOutward
Indicates that one entity’s religion is externally expressed, affiliated, or directed toward another entity or context.
-
D.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
E.
portraysReligionAs
Indicates that one entity represents, depicts, or characterizes a religion in a particular way.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 12:18 a.m.