Triple
T26990883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSI Services |
E679856
|
entity |
| Predicate | deliveryChannel |
P10739
|
FINISHED |
| Object | online remote proctoring |
—
|
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: online remote proctoring | Statement: [PSI Services, deliveryChannel, online remote proctoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryChannel Context triple: [PSI Services, deliveryChannel, online remote proctoring]
-
A.
deliveryPlatform
Indicates that one entity serves as the platform, service, or medium through which another entity’s delivery or distribution is carried out.
-
B.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
C.
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.
-
D.
deliveryMode
chosen
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
E.
deliveryTechnology
Indicates the method or system used to deliver a product, service, or content from a provider 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6218fc6308190b1e3317de86703db |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:51 a.m.