Triple
T7390639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Practice in Christianity |
E170487
|
entity |
| Predicate | preoccupiedWith |
P49999
|
FINISHED |
| Object | Christian discipleship |
—
|
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: Christian discipleship | Statement: [Practice in Christianity, preoccupiedWith, Christian discipleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preoccupiedWith Context triple: [Practice in Christianity, preoccupiedWith, Christian discipleship]
-
A.
obsessionWith
chosen
Indicates an intense, persistent, and often overwhelming preoccupation or fixation that one entity has toward another entity or object.
-
B.
engaged
Indicates that two entities are formally committed to enter into a marriage or long-term partnership with each other.
-
C.
oftenDedicatedTo
Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
-
D.
concern
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
E.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2216a5c8190a933b24fda4530d8 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.