Triple
T11034473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinematic Arts and Technology |
E260841
|
entity |
| Predicate | typicallyOfferedAs |
P9675
|
FINISHED |
| Object | undergraduate major |
—
|
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: undergraduate major | Statement: [Cinematic Arts and Technology, typicallyOfferedAs, undergraduate major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOfferedAs Context triple: [Cinematic Arts and Technology, typicallyOfferedAs, undergraduate major]
-
A.
usedAsOfferingAt
Indicates that something is employed or presented as an offering in a particular context, place, or event.
-
B.
offeredIn
chosen
Indicates that something is made available or provided within a particular context, setting, or medium.
-
C.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
D.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
E.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e709648190adbb05197e15ff76 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.