Triple
T34381921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisher of men |
E882460
|
entity |
| Predicate | thematicDomain |
P28568
|
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: [Fisher of men, thematicDomain, Christian discipleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicDomain Context triple: [Fisher of men, thematicDomain, Christian discipleship]
-
A.
thematicArea
chosen
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
-
B.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
-
C.
thematicTreatment
Indicates that one entity serves as the thematic focus, subject, or central topic treated, addressed, or explored by another entity.
-
D.
thematicFunction
Indicates how an entity participates in or contributes to the role structure of an event or situation (e.g., as agent, patient, instrument, etc.).
-
E.
classificationDomain
Indicates the conceptual or subject area within which an item is categorized or classified.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.