Triple
T29886279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLM ICL |
E759020
|
entity |
| Predicate | includesComponents |
P155142
|
FINISHED |
| Object | coursework |
—
|
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: coursework | Statement: [LLM ICL, includesComponents, coursework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesComponents Context triple: [LLM ICL, includesComponents, coursework]
-
A.
componentIncluded
chosen
Indicates that one entity is a constituent part or subcomponent that is contained within or included in another entity.
-
B.
isComponentAlongWith
Indicates that an entity functions as a component in conjunction with one or more other components, typically forming a combined or complementary unit within a larger whole.
-
C.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
D.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
E.
includesCommon
Indicates that two or more entities share at least one common element, component, or member within their respective sets or collections.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: April 29, 2026, 6 p.m.