Triple
T157185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Shepherd |
E3204
|
entity |
| Predicate | metaphorFor |
P834
|
FINISHED |
| Object | Jesus’ pastoral care for believers |
—
|
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: Jesus’ pastoral care for believers | Statement: [Good Shepherd, metaphorFor, Jesus’ pastoral care for believers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metaphorFor Context triple: [Good Shepherd, metaphorFor, Jesus’ pastoral care for believers]
-
A.
rhetoricalDevice
chosen
Indicates that one entity is used as a rhetorical device in relation to another, such as a figure of speech, stylistic technique, or persuasive strategy within a discourse.
-
B.
synonym
Indicates that two terms have the same or nearly the same meaning in a given context.
-
C.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
D.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
E.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25830136881909f5ecb2cb22097b2 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.