Triple
T24080384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langham Scholars |
E596485
|
entity |
| Predicate | supportsRoles |
P10797
|
FINISHED |
| Object | seminary faculty |
—
|
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: seminary faculty | Statement: [Langham Scholars, supportsRoles, seminary faculty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRoles Context triple: [Langham Scholars, supportsRoles, seminary faculty]
-
A.
supportsRole
chosen
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
B.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
C.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
requiresRole
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
-
E.
admittedRole
Indicates that an entity has been formally accepted or recognized as holding a particular role or position.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2351e08190857d57f266d1d4bf |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.