Triple
T157483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian theology |
E3210
|
entity |
| Predicate | hasSubdiscipline |
P5461
|
FINISHED |
| Object | biblical theology |
—
|
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: biblical theology | Statement: [Christian theology, hasSubdiscipline, biblical theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubdiscipline Context triple: [Christian theology, hasSubdiscipline, biblical theology]
-
A.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
B.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
C.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
D.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
E.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a257101060819094db0f3a3a72f312 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.