Triple
T14988152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master in the Study of Law |
E373759
|
entity |
| Predicate | modeOfDelivery |
P10739
|
FINISHED |
| Object | on-campus |
—
|
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: on-campus | Statement: [Master in the Study of Law, modeOfDelivery, on-campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfDelivery Context triple: [Master in the Study of Law, modeOfDelivery, on-campus]
-
A.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
B.
deliveryMode
chosen
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
C.
deliveryModelOf
Indicates that one entity functions as the delivery model or mechanism through which another entity (such as a service, product, or program) is provided or made available.
-
D.
formerlyDeliveryMode
Indicates that an entity previously used a particular delivery mode but no longer does so.
-
E.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7007588819095bb1de029a6f2eb |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.