Triple
T2286670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Theology |
E51405
|
entity |
| Predicate | websiteOfParent |
P69
|
FINISHED |
| Object | https://www.ptsem.edu/ |
—
|
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: https://www.ptsem.edu/ | Statement: [Department of Theology, websiteOfParent, https://www.ptsem.edu/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: websiteOfParent Context triple: [Department of Theology, websiteOfParent, https://www.ptsem.edu/]
-
A.
sponsorParentCompany
Indicates that a parent company provides sponsorship or support to another entity, typically through funding or resources.
-
B.
website
chosen
Indicates that one entity is the official website or web presence associated with another entity.
-
C.
parentService
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
-
D.
ultimateParentCompany
Indicates that one company is the highest-level controlling entity in a corporate ownership structure, with no parent company above it.
-
E.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc24730208190af8a5cf443d334f7 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.