Triple
T12789769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Adult Learning |
E305726
|
entity |
| Predicate | programCharacteristic |
P66086
|
FINISHED |
| Object | flexible scheduling |
—
|
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: flexible scheduling | Statement: [School of Adult Learning, programCharacteristic, flexible scheduling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programCharacteristic Context triple: [School of Adult Learning, programCharacteristic, flexible scheduling]
-
A.
programFeature
chosen
Indicates that a particular feature, capability, or component is part of, supported by, or provided within a given program.
-
B.
programmingCharacteristic
Indicates a relationship where an entity possesses or exhibits a particular property, trait, or quality specifically related to programming.
-
C.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
D.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
E.
programDesignation
Indicates that an entity is assigned or identified by a specific program designation or label.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6a61f48190972e241e70bc392c |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.