Triple
T8019028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS in Information Systems |
E186690
|
entity |
| Predicate | mayIncludeComponent |
P31918
|
FINISHED |
| Object | capstone project |
—
|
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: capstone project | Statement: [MS in Information Systems, mayIncludeComponent, capstone project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeComponent Context triple: [MS in Information Systems, mayIncludeComponent, capstone project]
-
A.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
B.
mayRequireComponent
chosen
Indicates that one entity can optionally depend on or need another entity as a component for its proper use or operation.
-
C.
mayIncludeUnitType
Indicates that something is allowed to contain or be associated with a particular type of unit.
-
D.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
E.
isPublicComponentOf
Indicates that one entity is a publicly accessible or externally visible part or module of another, larger entity or system.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df626e8819098a9f8908dfdad3b |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.