Triple
T7444795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five College Certificate in Buddhist Studies |
E171849
|
entity |
| Predicate | allowsCrossRegistration |
P57089
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Five College Certificate in Buddhist Studies, allowsCrossRegistration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsCrossRegistration Context triple: [Five College Certificate in Buddhist Studies, allowsCrossRegistration, true]
-
A.
hasCrossRegistration
chosen
Indicates that one educational institution allows students from another institution to enroll in its courses for credit.
-
B.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
C.
mayAlsoBeAccreditedTo
Indicates that the credit or attribution for something can additionally be assigned to another entity beyond the primary one.
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
supportsSecondLevelRegistrations
Indicates that an entity allows or enables second-level domain registrations directly under it.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f37054388190a6cb4c0db2ca6014 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.