Triple
T18917642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian views on virginity and celibacy |
E462761
|
entity |
| Predicate | regardAs |
P4529
|
FINISHED |
| Object | charism |
—
|
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: charism | Statement: [Christian views on virginity and celibacy, regardAs, charism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardAs Context triple: [Christian views on virginity and celibacy, regardAs, charism]
-
A.
regardsAsTool
Indicates that one entity views or treats another entity primarily as an instrument or means to achieve its own goals, rather than as an end in itself.
-
B.
observedAs
Indicates that one entity is perceived, recorded, or identified in the role, state, or form of another entity.
-
C.
arisesAs
Indicates that one entity comes into existence, develops, or emerges as a result, form, or manifestation of another entity or process.
-
D.
interpretedAs
chosen
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
E.
representsAs
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c62884988190a362ada1a0a47134 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.