Triple
T681876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroMasters programs |
E13199
|
entity |
| Predicate | timeToComplete |
P17474
|
FINISHED |
| Object | several months to over a year |
—
|
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: several months to over a year | Statement: [MicroMasters programs, timeToComplete, several months to over a year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToComplete Context triple: [MicroMasters programs, timeToComplete, several months to over a year]
-
A.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
B.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
-
C.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
D.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
runtimeMinutes
Indicates the total duration of something, typically a media work or process, measured in minutes.
- F. None of above. chosen
Provenance (4 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a06f9ee88190a2d757aacd8e3f5b |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.